Re: cygwin.bat improvements (was Re: Cygwin on XP disapearing terminal mystery)

[Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>]

On Wed, Feb 01, 2006 at 12:06:08PM -0500, Igor Peshansky wrote:
>However, most bash invocations should exit with a 0 exit code.  So, why
>not simply do something like the test below?
>
>if not errorlevel 1 goto nopause
>pause
>:nopause
>
>Also, "command not found" sets error code to 127, so the "1" above can be
>changed to "127".

Wouldn't that be:

  if not errorlevel 0 pause

or

  @if errorlevel 0 goto exit
  @echo "bash was either not executed or did not exit cleanly"
  @echo "[more touchy feely stuff here]"
  @pause
  :exit

?

This would be triggered if someone types "exit N" (where N != 0) in the
bash window, though.  I suspect that we'll now hear from the cygwin user
contingent who always type "exit 42" because that was required to work
around problems with ZoneAlarm v527.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/