Re: signals ignored in a subshell

From	Robert Elz <kre@munnari.OZ.AU>
Newsgroups	gnu.bash.bug
Subject	Re: signals ignored in a subshell
Date	2020-04-07 03:24 +0700
Message-ID	<mailman.282.1586204723.2644.bug-bash@gnu.org> (permalink)
References	(6 earlier) <16086.1586068489@jinx.noi.kre.to> <CAH7i3LrwPy9J9+8BPgvT+BGtv39nQJ2H-prxWXu7mHYZ8UjodQ@mail.gmail.com> <318.1586164329@jinx.noi.kre.to> <26616.1586188831@jinx.noi.kre.to> <16049.1586204681@jinx.noi.kre.to>

Show all headers | View raw

    Date:        Mon, 6 Apr 2020 15:44:08 -0400
    From:        Chet Ramey <chet.ramey@case.edu>
    Message-ID:  <20735a7e-627d-763b-adf6-0d94203aa6b4@case.edu>

  | You mean the terminal's input buffer, or readline's line buffer with
  | characters it's already read?

As a user I don't distinguish the two cases.   All I see is input I
have typed, that hasn't yet been handed away to be processed, and which
I can still edit and correct if I desire.   When using readline I have
a fairly powerful editor to assist, when not, it is just delete backwards
and retype, so the ease of corrections varies, but the overall effect is
the same.

In (I think) all cases except read -e when there is a SIGINT trap,
if I type ^C I abort what I am doing, and everything entered so far is
discarded (whether, when appropriate, it ends up in history for later
recall if desired is irrelevant - it doesn't get processed as valid
input).

kre

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

Thread

Re: signals ignored in a subshell Robert Elz <kre@munnari.OZ.AU> - 2020-04-07 03:24 +0700

csiph-web