>>>> "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.
Sometimes I wish raising up more robust users was an option. ;-)
The 100% CPU problem is a bug no matter how you look at it, and fixing
that bug seems to guarantee that XEmacs will die when the last console
device connection goes away. Try 21.4.10 (rc3 in the pretest
directory, or the public release in a couple of days).
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py