Paul,
Thk u for the quick response. I hope now this is the correct place to respond
to your email regarding my misunderstanding.
I'm answering my own raised questions from your response that others might
also learn from:
Yes my ignorance on the wild character substitution triggered by * and
Roman Rakus wrote:
> Aaah... so sorry, I'm bit confused. CATCH_SIGNALS is only on RHEL-4
> system. There is similar macro in quit.h called CHECK_TERMSIG. So the
> patch is:
OK. We're all on the same page now. :-)
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey,
> After some further investigation it turned out that you also need to use
> a function in your bash scripts to reproduce the bug.
>
> I have the following in my .bashrc
> mc () { MC=`/usr/bin/mc -P "$@"`; [ -n "$MC" ] && cd "$MC"; unset MC; }
>
> This was the recommended way for mc to 'remember'
Chet Ramey wrote:
After changing catching signals in bash - added CATCH_SIGNALS () macro -
we aren't catching them after calling execve(). This short patch fix it:
diff -up bash-3.2/execute_cmd.c.execve_catch_signal bash-3.2/execute_cmd.c
--- bash-3.2/execute_cmd.c.execve_catch_signal 2008-09-15
