5 Nisan 2020 Pazar tarihinde Robert Elz yazdı:
> Date:Sun, 5 Apr 2020 05:06:56 +0300
> From:=?UTF-8?B?T8SfdXo=?=
> Message-ID: w...@mail.gmail.com>
>
> | I was expecting it to work (i.e interrupt read again and call foo)
>
> Isn't that what it did?
No, it ignore
On 4/3/20 7:45 PM, Ami Fischman wrote:
> On Fri, Apr 3, 2020 at 9:13 AM Chet Ramey wrote:
>> Since this is all wrapped up in existing shell features, there's no good
>> way to isolate the fc behavior. I've seen suggestions on here to disable
>> set -v while running the DEBUG trap unconditionally,
On 4/4/20 1:32 AM, Oğuz wrote:
> While waiting for read builtin to complete, bash executes signal handlers
> in a subshell where signals are ignored.
It doesn't, though. What bash-5.0 does is to effectively block SIGINT
while executing a trap handler for SIGINT, since it doesn't let you run
SIGINT
On 4/5/20 5:42 AM, Oğuz wrote:
>> But I see what you mean now, during the read that's called from the
>> trap execution call of foo, SIGINT is blocked - that most probably should
>> not happen, and it looks as if when the trap handler exits, the
>> original read is resumed, that certainly shouldn'
On Sun, Apr 5, 2020 at 12:43 PM Chet Ramey wrote:
> Hence the discussion topic: should bash disable set -v when executing
> the DEBUG trap, should it do that just while running commands from a
> file while running `fc', or should it continue with its current behavior?
Thanks for clarifying the pa
