On Wed, Feb 01, 2006 at 01:31:08PM -0500, Igor Peshansky wrote: >On Wed, 1 Feb 2006, Christopher Faylor wrote: > >> 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". > >(actually Dave's right -- it's "9009"). > >> Wouldn't that be: >> >> if not errorlevel 0 pause > >Contrary to all common sense, "if not errorlevel A" means "if %ERRORLEVEL% >< A", not an equality test... So the above will *always* pause. Also, in >command.com (Win9x), I believe you can only have a "goto" after the "if >errorlevel" test...
Ok. I seem to vaguely recall this from MS-DOS days but I don't ever recall that only goto is allowed. I just tried this on Windows 98 and it is possible to put something besides a 'goto' in the if clause. Can anyone confirm/deny this on Windows 95? 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/
