Re: [Bug: 21.4.12] crash when X-display went away

Jim> Ok, thanks for the info. If any developer has the time to Jim> tell me, I wouldn't mind hearing why he/she doesn't think Jim> [xemacs as a server waiting for gnuclient] is desirable. The only opposition I know of is to committing one's own time to it. It doesn't look like an easy problem. Most users seem to really want XEmacs to exit when they log out. Admins don't like processes that don't go away, and might very well contain data the user wants to save, but they don't know. XEmacs can use up big hunks of VM; even if it's swapped out, that's not desirable. So we need to find ways to make that configurable, preferably at run time. AFAIK gnuserv connections aren't really first class citizens; XEmacs has to connect to some device. This means that it may be necessary to fiddle with the event loop. The crash that you observe suggests that this is so; the patch that stopped the Energizer bunny behavior was supposed to allow XEmacs to exit quietly. That it doesn't suggests that there's poorly understood behavior in there. Finally, there are any number of "session management" utilities (desktop.el, session.el, etc) that allow you to keep state across XEmacs invocations. Ie, if some hacker wants to make a hobby of this, fine. We'll look at the patches, and do what we can to help. But nobody here wants to open the can and start "worm farming." ;-) That's pretty much where I stand on it, anyway. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.