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. -- Q: How does a UNIX Guru do Sex ? A: unzip;strip;touch;finger;mount;fsck;more;yes;umount;sleep /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
