Hamish Moffatt wrote (Thu, 11 Dec 1997 18:36:55 +1100 ): |>On Wed, Dec 10, 1997 at 08:00:30PM -0800, Alan Su wrote: |>> Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ): |>> |>Hamish Moffatt <[EMAIL PROTECTED]> writes: |>> |> |>> |>> The window manager should always be last too. Specifically, the last |>> |>> command should not end in &, but it's most useful if that's the window |>> |>> manager. You could make it xclock or something, but then you'd |>> |>> have to kill the clock somehow to logout. |>> |> |>> |>Depends - most window managers will send a message to all active X |>> |>clients when they exit that causes them to shut down. |>> |>> I don't think this is right...I've fiddled a lot with window managers, |>> and I switch them ``mid-flight'' quite a bit. (Since I have an xterm |>> as the final exec'd command, killing my window manager doesn't end my |>> x session.) If what you're saying is true, every time I switch window |>> managers, all my windows would die, effectively ending the session. |>> Needless to say, this doesn't happen. |> |>The window manager will replace itself with the new one, |>(using an exec() call, presumably). So the same command in |>your .xsession/.xinitrc is still running. |>
This is only true if you use the window manager facility to restart. I usually kill the window manager with (kill <pid>), temporarily leaving me window manager-less. Then, I start another window manager from a shell I have open. I suppose I could configure my window manager to exec a different window manager, but that's too much effort. or i'm too lazy. (probably the latter.) -alan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .