While waiting for read builtin to complete, bash executes signal handlers
in a subshell where signals are ignored. See below.
$ foo() { trap foo INT; read; }
$ set -x
$ foo
+ foo
+ trap foo INT
+ read
^C++ foo
++ trap foo INT
++ read
^C^C^C
(the only way to exit is tapping enter twice; i.e finishi
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, like ksh93 does.
I've found https://groups.
On 4/2/20 12:50 PM, Ami Fischman wrote:
> After the editor invoked by edit-and-execute-command exits, the
> about-to-be-executed command (as edited by the editor) is echoed, but
> seemingly
> as if [set -v] was set, causing a command executed before the edited command
> as
> the result of a trap
