bug-bash
[Top][All Lists]
Advanced

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

Re: Fwd: Don't set $?=130 when discarding the current command line (not


From: Chet Ramey
Subject: Re: Fwd: Don't set $?=130 when discarding the current command line (not run yet) with CTRL-C?
Date: Thu, 26 Dec 2019 14:42:51 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.3.1

On 12/23/19 9:54 PM, Clark Wang wrote:
> Hi Chet,
> 
> On Fri, Nov 22, 2019 at 12:02 AM Chet Ramey <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     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.
> 
> 
> I don't know how many people count on this behavior. Is it possible this be
fixed?

There is nothing to `fix'; this is the intended behavior.


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



reply via email to

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