I know it's pretty insane to start an interactive shell in fvwm2
directly, but it would be nice if you could kill it nicely afterwards.
Executing next line in fvwm2 causes a freeze:
Exec read foo
I switched to the console, tried to kill the sh process with INT, HUP,
KILL with no success. After KILL ps tells that the process is defunct,
but I still can't continue working. Only killing fvwm2 with KILL
"works", but I'd prefer not to do that.
Is it hard to make fvwm2 a little more foolproof? ;-p
Regards,
Tung
--
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 Thu Sep 02 1999 - 07:37:51 BST