[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: signals ignored in a subshell
From: |
Robert Elz |
Subject: |
Re: signals ignored in a subshell |
Date: |
Tue, 07 Apr 2020 03:24:41 +0700 |
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
- Re: signals ignored in a subshell, (continued)
- Re: signals ignored in a subshell, Oğuz, 2020/04/05
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/05
- signals ignored in a subshell, Oğuz, 2020/04/06
- Re: signals ignored in a subshell, Oğuz, 2020/04/06
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/06
- Re: signals ignored in a subshell, Robert Elz, 2020/04/06
- Re: signals ignored in a subshell, Robert Elz, 2020/04/06
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/06
- Re: signals ignored in a subshell, Robert Elz, 2020/04/06
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/06
- Re: signals ignored in a subshell,
Robert Elz <=
Re: signals ignored in a subshell, Chet Ramey, 2020/04/05