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
On 9/24/13 2:54 AM, 李佳 wrote:
> Seems like bash tries to spawn a logout child process when received a SIGCONT
> signal and prepared to exit, unfortunately logout child process forked
> another children and etc. ok, that's only my guess, and somehow it does not
> have the same problem on Linux.
Hi, all:
I configured with default and installed bash-4.2.45 on AIX 5.3 to my home
directory. Each time I logged in, I used 'bash --login' to enter bash.
Accidentally I sent SIGSTOP to the process of bash, then sent SIGCONT. Bash put
the message 'There are running jobs' on screen, then forked
