I posted a while ago about the way e16 exits -- in particular, how other apps (like gvim) are affected by it...
http://sourceforge.net/mailarchive/message.php?msg_id=16523608 Bram Moolenaar of gvim fame seems to disagree: > On Sun, 18 Jun 2006 16:16:01 +0200, > Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Dennis Nezic wrote: > > > when i exit my wm (e16), since it doesn't (and shouldn't) close any > > other programs, gvim is stuck without an x server, and doesn't > > handle this loss gracefully. effectively, it's as if it was kill > > -9'ed ... and thus leaves temporary files behind, which i later > > have to labouriously clean up. > > > > can it not do something better .... like simply close down if no > > changes were made to the file (and close any temp files). and, i > > guess, leave the temp files behind if changes were made (as it > > currently does in all cases :\). > > Vim normally handles a shutdown of the window manager gracefully. > There is a protocol for this and Vim implements it. This may result > in the window manager not exiting when Vim has modified files. > > If you forcefully kill the window manager or the X server you will > get a hanging gvim (and possibly other programs). That's your own > fault then. > > If you shut down the window manager properly but Vim still hangs > somehow, perhaps the window manager doesn't work properly. You could > try another one. He seems to be making sense. ? _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
