From xemacs-m  Tue May  6 13:11:56 1997
Received: from CNRI.Reston.VA.US (CNRI.Reston.VA.US [132.151.1.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA12449
	for <xemacs-beta@xemacs.org>; Tue, 6 May 1997 13:11:55 -0500 (CDT)
Received: from newcnri.cnri.reston.va.us by CNRI.Reston.VA.US id aa15490;
          6 May 97 14:12 EDT
Received: from anthem.CNRI.Reston.Va.US by newcnri.CNRI.Reston.Va.US (SMI-8.6/SMI-SVR4)
	id OAA09106; Tue, 6 May 1997 14:12:09 -0400
Received: by anthem.CNRI.Reston.Va.US (SMI-8.6/SMI-SVR4)
	id OAA01944; Tue, 6 May 1997 14:11:56 -0400
Date: Tue, 6 May 1997 14:11:56 -0400
Message-Id: <199705061811.OAA01944@anthem.CNRI.Reston.Va.US>
From: "Barry A. Warsaw" <bwarsaw@CNRI.Reston.VA.US>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Hrvoje Niksic <hniksic@srce.hr>
Cc: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Re: Minibuffer and  multiple frames
References: <16594.862938741@rtp.ericsson.se>
	<kigd8r44hsz.fsf@jagor.srce.hr>
X-Mailer: VM 6.30 under 19.15 XEmacs Lucid
Reply-To: bwarsaw@python.org
X-Attribution: BAW
X-Oblique-Strategy: Credibility of Intentions
X-Url: http://www.python.org/~bwarsaw


>>>>> "Hrv" == Hrvoje Niksic <hniksic@srce.hr> writes:

    Hrv> Showing the minibuffer contents is wrong.  Every frame should
    Hrv> have its own minibuffer.  Not cycling it with `C-x o' is
    Hrv> right, too.

Both modes should be supported.  Some folks may want a minibuffer per
frame, but I'm pretty sure I would find it more useful to have a
single minibuffer that followed me around as I cycle through frames.

-Barry

