[ My apologies for suggesting actions you'd already tried
because I failed to read your original msg more carefully ]
>It turns what is normally invalid input into a hung process.
Yah, they're probably infringing on some M$ patent there.
>But the original problem is that I do not have job control,
>and I want it.
Well, the inability to suspend an app that's an immediate
descendant of the terminal emulator is a Feature not a
Bug so, as you suspected, you are going to have to go out
of your way to get this behavior. If you can't come up
with a less offensive hack you might try this:
At the end of your .bashrc you'd say:
.
.
.
.
if [ ! -z "$INTERACTIVE_COMMAND" ]
then
xyzzy="$INTERACTIVE_COMMAND"
unset INTERACTIVE_COMMAND
eval "$xyzzy"
fi
...and then you'd invoke your terminal emulator thus:
INTERACTIVE_COMMAND='set -m ; pine' xterm -e bash
I *did* say it was offensive, right? And pine may
still defeat you if its signal handling is truly strange
but, as I said, I don't have pine available to test...
*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************
