[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: |
Sun, 5 Apr 2020 17:45:22 -0700 |
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.
Of course, an alternative approach would be to enhance bash with a
nativefacility for coloring emitted command-lines, to obviate the need for DEBUG
in this context.
Cheers,
-a