bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Change in reaction to C-c (SIGINT) in an interactive shell


From: tschwinge
Subject: Change in reaction to C-c (SIGINT) in an interactive shell
Date: Wed, 07 Oct 2009 21:57:31 +0200

Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' 
-DCONF_OSTYPE='gnu' -DCONF_MACHTYPE='i486-pc-gnu' -DCONF_VENDOR='pc' 
-DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H   -I.  
-I../bash -I../bash/include -I../bash/lib   -g -O2 -Wall
uname output: GNU flubber 0.3 GNU-Mach 1.3.99/Hurd-0.3 i386-AT386 GNU
Machine Type: i486-pc-gnu

Bash Version: 4.0
Patch Level: 33
Release Status: release


Hello!

The 3.2 series of bash acted like this when the user is typing C-c
(SIGINT) in an interactive shell during command line editing: cancel the
command line editing, display a new prompt, set $? to 1.  With the recent
version, this changed as follows: cancel the command line editing,
display ^C, display a new prompt, set $? to 128.  The displaying of ^C is
in line with displaying it when a running process is being signalled,
where is also was displayed with bash versions 3.2 already.  But why the
value 128 for $? -- shouldn't this rather be 128 + SIGINT?

I don't care too much about this, but noticed it, and thought that I'd
bring it to your attention.


Regards,
 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]