Didier Verna <verna(a)inf.enst.fr> writes:
As I see it, here's what could happen:
- If you have a non X console connection somewhere, killing an existing X frame
won't indeed kill xemacs, but is likely to delete all X frames.
- If you don't have any non X connections, xemacs will be killed all the same.
I'm afraid you are right. The "correct" behaviour is that killing an
existing X frame deletes all the X frames *on that display*, not on
all displays. If you have only X frames running, it is normal that
XEmacs will exit -- as you say it yourself, that's how X handles
killing.
I have now tried my patch with multiple X connections and the result
is, well, bogus.
Still, I believe my patch should be applied because it at least
attempts to bring some order to the situation, and makes things work
with the TTY consoles.
The real pain is that X considers it fatal to loose a connection,
even in the case you have several ones.
Yuck! Is there a way around that?
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
A professor is one who talks in someone else's sleep.