[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: verbosity of DEBUG trap following edit-and-execute-command

From: Ami Fischman
Subject: Re: verbosity of DEBUG trap following edit-and-execute-command
Date: Fri, 3 Apr 2020 16:45:41 -0700

On Fri, Apr 3, 2020 at 9:13 AM Chet Ramey <address@hidden> 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.google.com/d/topic/gnu.bash.bug/_oG51FIMDE0/discussion
which suggests disabling [set -v] during the e-a-e-c but AFAICT doesn't talk
about the DEBUG trap. Or are you saying that e-a-e-c is implemented using DEBUG?

> What do you think? Should bash just disable set -v when running the DEBUG
> trap?

ISTM that yes set -v should be disabled during execution of the DEBUG trap.
Separately, I've also never appreciated the echoing that happens post-e-a-e-c,
but I do appreciate the echoing that !foo does when executing the last command
with a prefix of "foo", so I guess I don't have a principled stand to take on
that front :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]