Re: Problem with bash-3.0-9 (test)

2005-07-26 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Krzysztof Duleba on 7/26/2005 9:12 AM: > 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. This is a bug in bash and ksh; POSIX requires $? to ref

Re: Problem with bash-3.0-9 (test)

2005-07-26 Thread Krzysztof Duleba
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 no

Re: Problem with bash-3.0-9 (test)

2005-07-26 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 7/25/2005 12:53 PM: > According to David Rothenberger on 7/25/2005 12:32 PM: > >>>I tried out the new test version of bash-3.0 (bash-3.0-9) and noticed a >>>problem. When I press Ctrl-C at the bash prompt, bash itself exists

Re: Problem with bash-3.0-9 (test)

2005-07-25 Thread David Rothenberger
On 7/25/2005 11:53 AM, Eric Blake wrote: According to David Rothenberger on 7/25/2005 12:32 PM: I tried out the new test version of bash-3.0 (bash-3.0-9) and noticed a problem. When I press Ctrl-C at the bash prompt, bash itself exists. This happens when bash is started in a rxvt window or a re

Re: Problem with bash-3.0-9 (test)

2005-07-25 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to David Rothenberger on 7/25/2005 12:32 PM: > I tried out the new test version of bash-3.0 (bash-3.0-9) and noticed a > problem. When I press Ctrl-C at the bash prompt, bash itself exists. > This happens when bash is started in a rxvt window