I have some more information on this. In the latest test,
the problem occurs when I run bash under rxvt, but not when I run it under
xterm.
Using strace, I've found a difference in a call to rt_sigaction(). It calls
rt_sigaction(SIGTSTP, {SIG_DFL, ...})
under xterm (which works correctly), but
rt_sigaction(SIGTSTP, {SIG_IGN, ...})
under rxvt (where it doesn't).
I've been playing with rxvt and urxvt lately, which might explain why I've
seen the problem. Apparently there's some
difference between xterm and rxvt in the way they invoke the shell.
Details at:
https://gist.github.com/Keith-S-Thompson/c842663ace93c23fabd7
On Sat, Oct 31, 2015 at 12:45 PM, Keith Thompson <keithsthomp...@gmail.com>
wrote:
> $ trap
> trap -- 'show_error' ERR
> $ type show_error
> show_error is a function
> show_error ()
> {
> printf "\e[1mExit $?\e[m\n" 1>&2
> }
> $
>
>
> On Sat, Oct 31, 2015 at 12:00 AM, Andreas Schwab <sch...@linux-m68k.org>
> wrote:
>
>> Keith Thompson <keithsthomp...@gmail.com> writes:
>>
>> > For a while, I had two running login shells, one that had the problem
>> > and one that didn't. Comparing the output of "set" and "shopt" from
>> > both shells didn't show any differences that could explain this.
>>
>> What's the output of trap?
>>
>> Andreas.
>>
>> --
>> Andreas Schwab, sch...@linux-m68k.org
>> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
>> "And now for something completely different."
>>
>
>
>
> --
> Keith Thompson <keith.s.thomp...@gmail.com>
>
--
Keith Thompson <keith.s.thomp...@gmail.com>
