Kyle Jones <kyle_jones(a)wonderworks.com> writes in xemacs-beta(a)xemacs.org:
Are you sure this is a bug?
I am sure it is a bug, though I don't understand why Hrvoje is seeing
a situation reversed from what I see. I first experienced the problem
with olvwm and it _was_ fixed by a patch.
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. We have a variable, allow-deletion-of-last-visible-frame,
that lets you go ahead and delete the last visible frame. So far no
one has mentioned this variable's value.
The situation I was referring to shouldn't involve this variable. I
use virtual window managers and having a frame visible in an
undisplayed workspace shouldn't trigger this message. In any event, I
do not personally diddle with the value of
`allow-deletion-of-last-visible-frame' and the XEmacs behavior is
different between CDE and WindowMaker.
`allow-deletion-of-last-visible-frame' is a built-in boolean variable.
Value: t
Documentation:
*Non-nil means to assume the force option to delete-frame.
--
金がものを言う (Money talks)