Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Robert Elz <kre@munnari.OZ.AU>
Newsgroups: gnu.bash.bug
Subject: Re: signals ignored in a subshell
Date: Tue, 07 Apr 2020 03:24:41 +0700
Lines: 23
Approved: bug-bash@gnu.org
Message-ID: <mailman.282.1586204723.2644.bug-bash@gnu.org>
References: <20735a7e-627d-763b-adf6-0d94203aa6b4@case.edu> <3e31254d-cc8b-221c-ddb9-ea1ea9fa74c1@case.edu> <45c766ba-4489-bd7b-40c7-32fed37461f9@case.edu> <CAH7i3LqUZcV6shJv6nQoRkLp-zhBgTpWaUPKdzZwVC-W_0e8yw@mail.gmail.com> <23276.1586024838@jinx.noi.kre.to> <CAH7i3Lr5TTK+N-qC39+nmSo7jjhzDvPux39N4i2MyP5LCnnv5w@mail.gmail.com> <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>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1586204723 32441 209.51.188.17 (6 Apr 2020 20:25:23 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash@gnu.org
To: chet.ramey@case.edu
Envelope-to: bug-bash@gnu.org
In-Reply-To: <20735a7e-627d-763b-adf6-0d94203aa6b4@case.edu>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic]
X-Received-From: 2001:3c8:9009:181::2
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: <16049.1586204681@jinx.noi.kre.to>
X-Mailman-Original-References: <20735a7e-627d-763b-adf6-0d94203aa6b4@case.edu> <3e31254d-cc8b-221c-ddb9-ea1ea9fa74c1@case.edu> <45c766ba-4489-bd7b-40c7-32fed37461f9@case.edu> <CAH7i3LqUZcV6shJv6nQoRkLp-zhBgTpWaUPKdzZwVC-W_0e8yw@mail.gmail.com> <23276.1586024838@jinx.noi.kre.to> <CAH7i3Lr5TTK+N-qC39+nmSo7jjhzDvPux39N4i2MyP5LCnnv5w@mail.gmail.com> <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>
Xref: csiph.com gnu.bash.bug:16107

    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