Signals, process groups, sessions, orphans,
controlling terminals, etc. Here Be Dragons.
As an experiment, I'd suggest trying the exact
same scenarios but with vim instead of pine,
and then with xterm instead of gnome-terminal.
I'm guessing that pine's the culprit, though
I couldn't test that theory cuz I don't have
pine installed. I speculate that some of these
interactive apps first catch the SIGTSTP in order
that they can tidy up the display before altering
their signal handling and sending themselves a
second SIGTSTP, and it's possible that pine has
botched it where other apps like vim got it right.
*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************
