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

From	Clark Wang <dearvoid@gmail.com>
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-22 16:16 +0800
Message-ID	<mailman.2294.1574410659.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> <CADv8-ogRv-atdWkiRNWdVA=V03XKpq4AF1-pDTmc=PmKUiHK_w@mail.gmail.com>

Show all headers | View raw

On Fri, Nov 22, 2019 at 12:02 AM Chet Ramey <chet.ramey@case.edu> wrote:

>
> 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.
>

Curious why people care about this?

-clark

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? Clark Wang <dearvoid@gmail.com> - 2019-11-22 16:16 +0800

csiph-web