From xemacs-m  Mon Apr 21 16:38:13 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA00241
	for <xemacs-beta@xemacs.org>; Mon, 21 Apr 1997 16:38:12 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcmha22540; Mon, 21 Apr 1997 17:38:11 -0400 (EDT)
Date: Mon, 21 Apr 1997 17:38:11 -0400 (EDT)
Message-Id: <QQcmha22540.199704212138@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: Build Success - 20.2b1 - Linux2.0.28, but...
In-Reply-To: <m2ohb8gj2i.fsf@altair.xemacs.org>
References: <m2iv1hg0w7.fsf@sauna.ton.tut.fi>
	<m2hgh1obrn.fsf@altair.xemacs.org>
	<QQcmcx22856.199704201851@crystal.WonderWorks.COM>
	<m2iv1hsdau.fsf@sauna.ton.tut.fi>
	<QQcmdo26168.199704202313@crystal.WonderWorks.COM>
	<m2ohb8gj2i.fsf@altair.xemacs.org>
X-Mailer: VM 6.28 under 20.2 XEmacs Lucid (beta1)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Steven L Baur writes:
 > Kyle Jones <kyle_jones@wonderworks.com> writes:
 > 
 > > Pretty grisly.  Reading from the minibuffer at this point is
 > > essentially calling Frecursive_edit from within a menubar
 > > callback.  The new command loop is eating the events the old
 > > command loop was expecting to get.  When Frecursive_edit
 > > returns the menubar code has invalid state information and
 > > abort()s.
 > 
 > O.K.  That makes sense.  How do we fix^H^H^Hput a bandaid on this?
 > The customize menu is pretty terrifying in all the packages it loads
 > and requires an unusual amount of dexterity to navigate, could we
 > remove it for the time being?

Anything that can cause the menubar widget state to be fiddled
with can cause a crash if it is called from a menubar :filter
callback.  It probably applies to :selected and :active callbacks
also, but I haven't verified that.

At the very least this means that Fnext_event/next-event calls
must signal an error if called from within the guts of the menu
code.  A simple semaphore like in_menubar ought to do it, ugly
though it is.

As for the Customize menu, I'm currently of the opinion that all
the defcustoms should be slurped out of all the bundled packages,
dropped into a file, and dumped with XEmacs.  Hopefully this
would get rid of the need to load all that stuff on the fly from
the menus.

