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

[Chet Ramey]

tschwinge@gnu.org wrote:
> 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?

Thanks for the report.  This has already been fixed for bash-4.1.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/