Re: when ssh dies, xemacs doesn't
Stephen J. Turnbull wrote:
>>>>> "Rick" == Rick Campbell <rick(a)campbellcentral.org>
writes:
Rick> the should-be-dead XEmacs
Why _should_ it be dead? We go to a lot of trouble to ensure that
loss of a display connection doesn't kill XEmacs; to ensure that other
processes can connect to a running XEmacs as a server; and even
provide a way that a server XEmacs can be embedded via a client widget
in another process. Yeah, I know, "principle of least astonishment":
other editors die when the console goes away, XEmacs should seppuku too.
Now you're just being silly.
Even if you fixed the "100%" bug, it serves no useful purpose that the
default state should be, "every time I log out and back in, I end up
with an idle xemacs process hogging memory."
If you made it so that when someone ran "xemacs" again, with no
arguments, it transparently re-attached, that would be a good trick,
but that's not how it works.
This stay-alive nonsense should be an option, off by default.
--
Jamie Zawinski
jwz(a)jwz.org http://www.jwz.org/
jwz(a)dnalounge.com http://www.dnalounge.com/