Jason Kibblewhite wrote:
> Well hardly being the expert here but all the window managers that I've
> tried also do this. Those including Window Maker, AfterStep, E, TWM,
> Olvwm and a few others hardly worth mentioning. I just use the start from
> xterm and exit the xterm which seems to work just fine for me.
It probably depends on your shell and how it behaves when recieving
signals, it might depend on you terminal emulator but I expect they all
behave the same, it won't depend on your window manager.
When your terminal emulator is killed by the window manager it will send
a -HUP signal to the shell it is running. Most shells react to -HUP by
killing all their children (with -HUP so it can propogate) and exiting.
Killing the shell -KILL will just kill it with no chance of it being
able to interfere with its children. Exiting a shell may or may not kill
its children, it depends on the shell and is probably configurable.
You can prevent -HUP from propogating to children with the nohup command
though it tends to create nohup.out files.
Cheers,
Tim.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Oct 13 1999 - 03:36:44 BST