Problem with bash-3.0-9 (test)

Krzysztof Duleba krzysan@skrzynka.pl
Tue Jul 26 16:17:00 GMT 2005


Eric Blake wrote:

> Something weird is going on.  Once I have a shell open, and fire up a
> second level bash (non-login), Ctrl-C behaves correctly and cancels the
> current line input with exiting the shell.  But then when I type exit,
> bash returns with exit status 1, even though it did absolutely nothing and
> should be returning 0.  (On a possibly related note, in ksh, typing Ctrl-C
> then exiting gives exit status 130, instead of 0; but zsh gets it correct
> and returns 0).

Isn't this caused by the fact that bash returns $? when exits and Ctrl-C 
sets $? to 1? ksh, on the other hand, sets $? to 130 after Ctrl-C.

Krzysztof Duleba


--
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/



More information about the Cygwin mailing list