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

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: verbosity of DEBUG trap following edit-and-execute-command
Date	2020-04-06 09:18 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.245.1586179093.2644.bug-bash@gnu.org> (permalink)
References	(1 earlier) <35304daa-1838-b761-1925-d48becb0fa31@case.edu> <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>

Show all headers | View raw

On 4/5/20 8:45 PM, Ami Fischman wrote:
> On Sun, Apr 5, 2020 at 12:43 PM Chet Ramey <chet.ramey@case.edu> 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 parameter space.
> For my purposes either of the first 2 options would work, but my only use of
> DEBUGhas been to muck with terminal state this way, so possibly users of DEBUG
> withless-visible side-effects would prefer it to stay as-is. Not sure if such
> usages exist orhow to trade-off the use-cases against each other.

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.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

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

Thread

Re: verbosity of DEBUG trap following edit-and-execute-command Chet Ramey <chet.ramey@case.edu> - 2020-04-06 09:18 -0400

csiph-web