On 10/30/17 8:06 AM, Boruch Baum wrote:
> Is there a way to optionally turn off the verbose option for traps when
> running 'fc'? Toggling the verbose option from the command line only
> makes things more verbose for me (it echoes $PROMPT_COMMAND).
>
> For me, the desirable behavior would be for
On 2017-10-28 15:40, Chet Ramey wrote:
> On 10/27/17 10:53 AM, Eduardo Bustamante wrote:
> > On Fri, Oct 27, 2017 at 1:21 AM, Boruch Baum wrote:
> >> In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap
> >> in my .bashrc and tried running the following command, with the
> >> fo
On 10/27/17 10:53 AM, Eduardo Bustamante wrote:
> On Fri, Oct 27, 2017 at 1:21 AM, Boruch Baum wrote:
>> In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap
>> in my .bashrc and tried running the following command, with the
>> following output resulting. The five lines between
On Fri, Oct 27, 2017 at 1:21 AM, Boruch Baum wrote:
> In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap
> in my .bashrc and tried running the following command, with the
> following output resulting. The five lines between the command being run
> by fc and that command's outp
In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap
in my .bashrc and tried running the following command, with the
following output resulting. The five lines between the command being run
by fc and that command's output, is the text of the DEBUG trap.
1075 $ fc -e true 1072 1
