On Mon, Nov 25, 2002 at 09:39:19AM -0500, Sean Proctor wrote: > I don't think I'm missing the point. It's easy to get gnome-session > to not start a window manager. I can go into sessions and trash > metacity and it's gone, and I get no window manager the next time I > log in. so I have to go to a terminal and start metacity.
Ah, thanks, that provided some useful info to understand the problem. Window Maker doesn't show up in the list of running applications, which means that when saving a session, you'll effectively remove the window manager from the list of applications that should be started next time. Interestingly enough this is also the answer to my other problem (a 10 second delay between starting Window Maker and the other programs). Since Window Maker isn't doing the session dance, gnome-session seems to wait for a while for it to start before giving up and moving on. This still makes changing the window manager a very weird process. You can add gnome-wm to the list of start-up applications, but if you select "save session" when logging off, the current window manager will be saved, not gnome-wm. That is, even if gnome-wm paid attention to the key the documentation mentions, it wouldn't make a difference because a specific window manager is stored in the session, not "gnome-wm". For some reason I had thought gnome-session treated the window manager in a special way. Greetings, Marcelo
