Re: looking for consistent C-c trap behavior

From	gentoo_eshoes@tutanota.com
Newsgroups	gnu.bash.bug
Subject	Re: looking for consistent C-c trap behavior
Date	2020-04-20 00:02 +0200
Message-ID	<mailman.735.1587333754.3066.bug-bash@gnu.org> (permalink)
References	(1 earlier) <a8b7d5fc-0a64-0a0e-bd49-7f808f937813@case.edu> <M5EEHGq--3-2@tutanota.com> <M5ESsGC--3-2@tutanota.com> <450694da-135a-8eb7-f61f-aacbb20df8a9@case.edu> <M5JSfxA--B-2@tutanota.com>

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw


Apr 19, 2020, 21:20 by chet.ramey@case.edu:

> On 4/18/20 6:45 PM, gentoo_eshoes@tutanota.com wrote:
>
>>
>>
>> The code that allows 'read -p' to be interrupted when posixly_correct, must then be somewhere else, I shall keep lookin', yet I fear I might not find it :-"
>>
>
> Look in read_builtin() and the calls to various zread* functions there.
>
Excelent! Thank you very much for this useful information!
with it I was able to make the necessary local-only changes for myself (patch attached)
I also did this:
> This is a reasonable idea for posix mode, since the trap action is run
> after the read command returns.
^ in context here: https://lists.gnu.org/archive/html/bug-bash/2020-04/msg00116.html

Much appreciated, Chet!
Cheers!

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

Thread

Re: looking for consistent C-c trap behavior gentoo_eshoes@tutanota.com - 2020-04-20 00:02 +0200

csiph-web