From xemacs-m  Sat Mar 15 20:44:37 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 UAA28878
	for <xemacs-beta@xemacs.org>; Sat, 15 Mar 1997 20:44:35 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQchbe25095; Sat, 15 Mar 1997 21:44:35 -0500 (EST)
Date: Sat, 15 Mar 1997 21:44:35 -0500 (EST)
Message-Id: <QQchbe25095.199703160244@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: dired/gnus on a tty
In-Reply-To: <kig7mj8fv56.fsf@jagor.srce.hr>
References: <199703152215.XAA13530@sol1.cybernet-ag.net>
	<kigybboiygo.fsf@jagor.srce.hr>
	<yvialo7oep8a.fsf@atreides.eng.mindspring.net>
	<kiglo7og0u4.fsf@jagor.srce.hr>
	<yviaiv2seksl.fsf@atreides.eng.mindspring.net>
	<kigbu8kfygm.fsf@jagor.srce.hr>
	<QQchay23723.199703160107@crystal.WonderWorks.COM>
	<kig913ofxbn.fsf@jagor.srce.hr>
	<QQchbb24285.199703160145@crystal.WonderWorks.COM>
	<kig7mj8fv56.fsf@jagor.srce.hr>
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

Hrvoje Niksic writes:
 > Kyle Jones <kyle_jones@wonderworks.com> writes:
 > 
 > > Under FSF Emacs menu-bar-mode controls whether menus are displayed.
 > > It doesn't specify maenus can be displayed.
 > 
 > Then how did one know whether menus could be displayed in GNUmacs
 > before 19.30 (IIRC that's when the tty menus were implemented).

Simple.  If you were on a tty, there are no menus.  Having seen
the tty based ``menu support'' in 19.34, this is still true as
far as I'm concerned.

 > > Whether the menubar is currently visible or not, programs that have
 > > menus should setup the menubar anyway, because the user might turn
 > > on the menubar later.  The same is true for the toolbar.
 > 
 > OK.  But then the matter of device-localness is irrelevant anyway,
 > because (in a correct implementation):
 > 
 > 1) you setup the menubar and toolbar the way you'd like them to be,
 >    regardless of whether they'll be displayed;
 > 2) on the devices that can display them, the user can choose if
 >    they'll be displayed using menu-bar-mode and such;
 > 3) on the devices that can't display them, they won't be displayed;
 > 4) a user should be able to have the same buffer moved from device to
 >    device, with the menus correctly displayed in the devices that can
 >    display them, and without errors on devices that can't display
 >    them.
 > 
 > How close is XEmacs to the state described by these 4 points?

It is irrelevant for buffer specific instances of objects, but
not for frames.  It is a waste of time to try to attach a toolbar
specification to a tty frame.  Might even generate an error.

 > > There's also the matter of popup menus, whose function is unrelated
 > > to whether the menubar is visible or not.
 > 
 > They should be covered with the above.

Not quite.  A function that wants to call popup-menu needs to
know whether the currently selected device can display a menu.
Calling popup-menu does nothing at all on a tty.  And there's
floating-toolbar to consider.

