Re: Fwd: Don't set $?=130 when discarding the current command line (not run yet) with CTRL-C?

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Fwd: Don't set $?=130 when discarding the current command line (not run yet) with CTRL-C?
Date	2019-11-21 11:02 -0500
Message-ID	<mailman.2211.1574352170.13325.bug-bash@gnu.org> (permalink)
References	<CADv8-ogKo=wDshxPiJj8D+BydvcOFS99KQ5pDjWCu7a1v=8nwQ@mail.gmail.com> <CADv8-oi+7MQ042_cAjtPrr4Jm=EFjjFLHGxSOPpWwF3066uotA@mail.gmail.com> <4b15601c-1b0d-01c5-990e-7fdf4600fb9e@case.edu>

Show all headers | View raw

On 11/20/19 9:27 PM, Clark Wang wrote:
> It's quite common for people to press CTRL-C to discard the current command
> line. This is harmless actually for most times except when people include
> $? in $PS1. I also show $? in red color when it's not 0 so it's more
> noticeable. So is it OK to not change $? when people are pressing CTRL-C to
> discard the input?

This behavior dates from at least 2009 and was added at user request so
they could tell exactly that: whether or not entering the last command had
been interrupted by a signal.

(Before that, dating back to bash-4.0, it set $? to 128 for exactly the
same reason, but that's clearly wrong. Before that, it set $? to 1 for as
far back as I have bash versions built, but that doesn't tell you anything
about signal receipt.)

Chet

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

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Fwd: Don't set $?=130 when discarding the current command line (not run yet) with CTRL-C? Chet Ramey <chet.ramey@case.edu> - 2019-11-21 11:02 -0500

csiph-web