"Steffl, Erik" wrote:
> my point is that simply quitting fvwm should leave the rest
> of X (other programs) untouched - I might want to start
> another window manager, I might be using different session
> manager etc... (and that's what fvwm currently does, I am
> advocating status quo)
AFAIUI, if 'fvwm2' is the last thing in your .xinitrc, then quitting it
will terminate that script and X will terminate (forcing your app.s to die
as well).
I have to say, though, that (under Solaris at least) ISTR *sometimes*
getting a situation where for some reason a live child process caused X to
think the script hadn't terminated; it happens so rarely that I've never
bothered to investigate.
I run 'fvwm2 &' myself, then run a noddy prog. 'X-session' at the end of
my .xinitrc that does nothing but sleep. This allows me to exit fvwm &
restart it or something else without logging out, and I've not had
problems for a couple of years or more with this method. Of course, your
main-menu 'Exit' needs to kill this process (I have a util. to effectively
'kill -9 `ps | grep foo | awk "print $1"`').
All of which is rather OT ...
--
=====================- http://www.racaldefence.com/ -===================
Neil Bird |
| This .signature is
mailto:neil.bird_at_rdel.co.uk | certified Y2K compliant
--
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 Jan 06 2000 - 03:05:30 GMT