Hrvoje Niksic <hniksic(a)srce.hr> writes:
Kyle Jones <kyle_jones(a)wonderworks.com> writes:
> Are you sure this is a bug? The point of the check, obviously, is
> to prevent you from being left with just unmapped frame and thus
> have no way to control the running XEmacs.
It's a bug. I am not talking about the last XEmacs frame, but about
the last frame on any one workspace. That means that if I configure
Gnus or VM to start up in a separate frame on a different workspace, I
can't exit it without the FORCE argument.
Still, it's not a bug in XEmacs, but rather a misconception of the X
Windows' states[1] and the way window managers achieve their desired effect.
Basically, what happens is that a window on another desktop is really
unmapped in the X sense, and XEmacs has no way to know that this window can be
visible again (thanks to a WM command).
In the best situation, some window managers will supply more
information through a specific communication protocol, which means that if we
want to improve XEmacs' concept of window states, we'll have to write specific
code for all window managers on earth.
In the worst case, some window managers won't give you any
information. For them, it will be impossible to fix the problem you describe.
Footnotes:
[1] To be honest, at the time X was written, there was probably no concept of
workspace yet.
--
/ / _ _ Didier Verna
http://www.inf.enst.fr/~verna/
- / / - / / /_/ / ENST, INFRES C201.1 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46
75013 Paris, France Fax. +33 (1) 45 81 31 19