Path: csiph.com!5.us.feeder.erje.net!feeder.erje.net!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: Sun, 19 Apr 2020 00:45:07 +0200 (CEST)
Lines: 32
Approved: bug-bash@gnu.org
Message-ID: <mailman.634.1587249913.3066.bug-bash@gnu.org>
References: <M58iOBd--3-2@tutanota.com> <a8b7d5fc-0a64-0a0e-bd49-7f808f937813@case.edu> <M5EEHGq--3-2@tutanota.com> <M5ESsGC--3-2@tutanota.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: bug-bash@gnu.org, chet.ramey@case.edu
To: Chet Ramey <chet.ramey@case.edu>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <M5EEHGq--3-2@tutanota.com>
Received-SPF: pass client-ip=81.3.6.162; envelope-from=gentoo_eshoes@tutanota.com; helo=w1.tutanota.de
Precedence: list
Xref: csiph.com gnu.bash.bug:16170




Apr 18, 2020, 23:41 by gentoo_eshoes@tutanota.com:

>
> On another note, I naively tried to patch out the POSIX requirement, for =
my own/local_use puposes but had no effect:
> in this code
> +=C2=A0 /* posix mode SIGINT during read -e. We only get here if SIGINT i=
s trapped. */
> +=C2=A0 if (posixly_correct && this_shell_builtin =3D=3D read_builtin && =
sig =3D=3D 2)
> +=C2=A0=C2=A0=C2=A0 {
> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 last_command_exit_value =3D 128|SIGINT;
> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 throw_to_top_level ();
> +=C2=A0=C2=A0=C2=A0 }
> by removing "posixly_correct &&" from above. I've no idea why that would =
have no effect, a bit stumped.
> I've even tried with a prior 'make clean'. The only explanation is that s=
ome other code that happens only during `POSIXly correct` mode is affecting=
 this somehow...
>
regarding the above, I stand corrected: it does indeed have effect but only=
 on 'read -e' (just as the comment states), that bash_event_hook() function=
 isn't entered for 'read -p' which to me was surprising, yet no doubt corre=
ct(I'm guessing).
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 :-"