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

Path	csiph.com!eternal-september.org!feeder.eternal-september.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
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	Thu, 21 Nov 2019 11:02:39 -0500
Lines	23
Approved	bug-bash@gnu.org
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>
Reply-To	chet.ramey@case.edu
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding	7bit
X-Trace	usenet.stanford.edu 1574352171 32310 209.51.188.17 (21 Nov 2019 16:02:51 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	chet.ramey@case.edu
To	Clark Wang <dearvoid@gmail.com>, "bash.bug list" <bug-bash@gnu.org>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574352161; bh=6w4SCMWpIjIWsb1IJZlOZdO4LByiMq75CDNYPU4bShc=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ucvkitM8SvjcVoq7/xyPbAbjV9onAYnR8Msq8gf5taTZXnoHjN9LBcky54iqu1DQig 6+Do0SavPM4eilmo6k6d8g36p4rTzEk8m7ZRKkznqJ9+ZxOST2HPAEt1BxxLp/6FkOL w4vEq/aBeWz4bK5xTjPxYlojLfTEpIwXv+d5WHzZnAmkBC/nMbrT2uCTdPFNSeJVuM9 3MOAl4yOvUI6ztNNpC5LpIPTIQ4bUg0Vp0qUFxjV7JqGm/dDZK0Knwux62SjJ6P6WKT C9inlOufkTOZF2Kbvx1UY4pE/3r8ViE/WQO+/wjN/HaJe8dmCbXViS02T4oby3IeocR MVxTBGSQ==
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574352160; bh=+YWyhu1uBmrMyf92t4bowmWrg5jTXPrZIMZB7WkJ4fY=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Z5kD29gM9ndJ0Edq7EFS+V8Ewt7HgYWKpyFTp01jld7mbRnRzy/qmt3hGzWd2ROAmF GP6jZ6jNghX96lU/IQCp3uM9icsazmOlKig5ngKN9TRCsep+dVghIQpMxlcovFp+Xgn rXv27SzOhI16wjnzDJGoJGHkejvywYmWPOY6LMt01fLFO6mQcUO38WB5hMN6+o5sm4C mWlAepQaDGI0Q6mWIzQ7ufNOdzyaDKTOBfCF1MPHim4UncUNQ97pVOzsSl0p8B7RmWQ lY91t7q44xjeutz8dLHfi6cgkDe8Ra4YOKKqV440em3M06vn5O426FYiSDKWKlCzF4w y5ikFvSw==
User-Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
In-Reply-To	<CADv8-oi+7MQ042_cAjtPrr4Jm=EFjjFLHGxSOPpWwF3066uotA@mail.gmail.com>
Content-Language	en-US
X-Junkmail-Status	score=7/90, host=mpv3-2015.case.edu
X-Junkmail-PrAS-Raw	score=7/90, refid=2.7.2:2019.11.21.145116:17:7.944, ip=, rules=DKIM_SIGNATURE, __HAS_REPLYTO, __HAS_CC_HDR, __SUBJ_REPLY, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __HAS_REFERENCES, __REFERENCES, __HAS_FROM, FROM_EDU_TLD, __HAS_MSGID, __SANE_MSGID, DATE_TZ_NA, __USER_AGENT, __MOZILLA_USER_AGENT, __MIME_VERSION, __IN_REP_TO, __CT, __CT_TEXT_PLAIN, __CTE, __REPLYTO_SAMEAS_FROM_ADDY, __REPLYTO_SAMEAS_FROM_ACC, __FROM_DOMAIN_IN_ANY_CC1, __FROM_DOMAIN_IN_ANY_CC2, __REPLYTO_SAMEAS_FROM_DOMAIN, __DKIM_ALIGNS_1, __DKIM_ALIGNS_2, __ANY_URI, __URI_MAILTO, __URI_WITH_PATH, __URI_NO_WWW, __CP_URI_IN_BODY, __INVOICE_MULTILINGUAL, __FRAUD_MONEY_CURRENCY_DOLLAR, __SUBJ_ALPHA_NEGATE, __URI_IN_BODY, __URI_NOT_IMG, __FORWARDED_MSG, __BODY_NO_MAILTO, __NO_HTML_TAG_RAW, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_900_999, __MIME_TEXT_P1, __MIME_TEXT_ONLY, __URI_NS, [TRUNCATED], so=2010-03-03 19:42:08, dmn=2016-08-03-0138
X-detected-operating-system	by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy]
X-Received-From	129.22.103.194
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.23
Precedence	list
List-Id	Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe	<https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive	<https://lists.gnu.org/archive/html/bug-bash>
List-Post	<mailto:bug-bash@gnu.org>
List-Help	<mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe	<https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID	<4b15601c-1b0d-01c5-990e-7fdf4600fb9e@case.edu>
X-Mailman-Original-References	<CADv8-ogKo=wDshxPiJj8D+BydvcOFS99KQ5pDjWCu7a1v=8nwQ@mail.gmail.com> <CADv8-oi+7MQ042_cAjtPrr4Jm=EFjjFLHGxSOPpWwF3066uotA@mail.gmail.com>
Xref	csiph.com gnu.bash.bug:15623

Show key headers only | 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