>>>> "J" == J <jmarant(a)nerim.net> writes:
> Hi Jérôme, which xemacs version are you using?
J> This is xemacs21-nomule 21.4.13 from Debian unstable (no mule
J> and no GTK).
J> The problem is that once in the infinite loop, I can't do
J> anything to to stop XEmacs. C-g doesn't even work. I can't even
J> kill XEmacs by sending a "close window" event to it. Only,
J> killing the process works.
I think this is the known bug where Metacity insists on maximizing to
the pixel, but XEmacs wants character cell sizes. For some reason,
the negotiation gets into a loop. Sometimes (if the hardware is not
too fast) the loop is visible as flickering in the upper-right corner.
I tend to suspect that Metacity is not putting its foot down and
saying "this is your geometry---live with it", which is what the
parent window is supposed to do. I'm pretty sure that XEmacs does its
geometry negotiation properly according to Xt standards; I know that
GNOME basically does not care if non-GNOME applications work (that is,
it's definitely a secondary priority and in practice it rarely gets
much attention). I think if you use the GNOME build it will work fine.
I will be looking at the XEmacs routines, but if it's something that
needs to work around a window manager that doesn't conform to Xt, it
may take a while to fix because the first priority is to conform to
the standard we implement.
J> However, I ran it into gdb and stopped it many times. I think
J> it has something to do with emacs_Xt_event_handler.
So does everything: every external interaction goes through that
handler. That routine is just a dispatcher.
--
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.