On 9/24/13 11:45 AM, Carlos Pita wrote:
> I see that, Chet. But it's not necessarily supposed to be echoed,
> that's what I'm saying. It's counterintuitive that fc prints the
> output. In fact, the output could very confusing.
OK. Here's how fc has worked historically: it internally turns on the
I see that, Chet. But it's not necessarily supposed to be echoed,
that's what I'm saying. It's counterintuitive that fc prints the
output. In fact, the output could very confusing. I have a complicated
expression in the DEBUG trap that doesn't produce any output by
itself, but this is what I see af
On 9/19/13 2:12 PM, Carlos Pita wrote:
> Bash Version: 4.2
> Patch Level: 45
> Release Status: release
>
> Description:
>
> If you set a DEBUG trap fc echoes it along the edited commands after
> leaving editor.
Sure: the DEBUG trap is supposed to be executed before every simple
command (and a
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash
