Re: looking for consistent C-c trap behavior

Path	csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From	gentoo_eshoes@tutanota.com
Newsgroups	gnu.bash.bug
Subject	Re: looking for consistent C-c trap behavior
Date	Mon, 20 Apr 2020 00:02:22 +0200 (CEST)
Lines	73
Approved	bug-bash@gnu.org
Message-ID	<mailman.735.1587333754.3066.bug-bash@gnu.org> (permalink)
References	<M58iOBd--3-2@tutanota.com> <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>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	multipart/mixed; boundary="----=_Part_163719_1613418781.1587333742949"
X-Trace	usenet.stanford.edu 1587333755 31959 209.51.188.17 (19 Apr 2020 22:02:35 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	chet.ramey@case.edu, bug-bash@gnu.org
To	Chet Ramey <chet.ramey@case.edu>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1587333742; s=s1; d=tutanota.com; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=M9ie7nKyY9SX3n5UU7RBX7nfPC8QzPml+HyTeROCziU=; b=t/GJ7Ql0oykoGjWrsCWKYqORrFGhxj4PCNwQuivanljGoXgj5Y0JMwnp1UVo6zYW OdBN2T+tdB1juIgXv42va3uzKesL0OYpk04hZG7CmekI5+y92A0PLInmdDgEGEo58B3 6Y6gSyxL+gfeDBf8yED4WNUxHHNSaOhkIbjKQdutjwFnhxi4tURgLuPksUbcC/QT5+G W8zxnlpfiG7FB5vRVQhbdfUJFiw2fxI2McT4laJHrsENCS5NH0bXo+LcpGrpdsNtGsM JRixEGAf1mF/dtTUJQanr0wkJqe2iK+UjnRv/lBuWFsEqavkErGcGpUXZAL+XSrMLsT esDw4PXM9g==
In-Reply-To	<450694da-135a-8eb7-f61f-aacbb20df8a9@case.edu>
Received-SPF	pass client-ip=81.3.6.162; envelope-from=gentoo_eshoes@tutanota.com; helo=w1.tutanota.de
X-detected-operating-system	by eggs1p.gnu.org: Linux 2.2.x-3.x [generic] [fuzzy]
X-Received-From	81.3.6.162
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	<M5JSfxA--B-2@tutanota.com>
X-Mailman-Original-References	<M58iOBd--3-2@tutanota.com> <a8b7d5fc-0a64-0a0e-bd49-7f808f937813@case.edu> <M5EEHGq--3-2@tutanota.com> <M5ESsGC--3-2@tutanota.com> <450694da-135a-8eb7-f61f-aacbb20df8a9@case.edu>
Xref	csiph.com gnu.bash.bug:16180

Show key headers only | 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