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

From	Ami Fischman <ami@fischman.org>
Newsgroups	gnu.bash.bug
Subject	Re: verbosity of DEBUG trap following edit-and-execute-command
Date	2020-04-11 11:59 -0700
Message-ID	<mailman.30.1586631607.3066.bug-bash@gnu.org> (permalink)
References	(2 earlier) <CAGKqTXW7=9wuHimeTQy2dH5MTjfpCsnGFJmkmPL0U56Y6TfmPg@mail.gmail.com> <ce0869ac-4773-7ac4-8bab-e1b82fe2837e@case.edu> <CAGKqTXWg_z6a76v5PCKcFQXmL+reCaef=zybrDJc8=vxBoxg6w@mail.gmail.com> <4208af10-a3ab-cb6e-7d57-f30fc9668eca@case.edu> <CAGKqTXUnRfPZP_sd2DM5Scx6prfkk=ShFsg_T61g4Yuug5xDgA@mail.gmail.com>

Show all headers | View raw

On Mon, Apr 6, 2020 at 6:18 AM Chet Ramey <chet.ramey@case.edu> wrote:
> I'm going to go with a variant of 2: a more general facility that only the
> `fc' builtin uses. It will be in the next devel branch push.

Thanks!  Confirmed that patching trap.{h,c} and builtins/fc.def
to reproduce the diffs in those files from
http://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=e34adc2c3b6b8722d0316f3b26fe5346faf94dea
makes bash behave the way I was hoping.
("patching" instead of just building at HEAD b/c I'm a deb
amateur but wanted to stick as close as possible to the bash I
get normally in this environment)

Cheers,
-a

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: verbosity of DEBUG trap following edit-and-execute-command Ami Fischman <ami@fischman.org> - 2020-04-11 11:59 -0700

csiph-web