From xemacs-m  Tue May  6 12:13:13 1997
Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id MAA10485
	for <xemacs-beta@xemacs.org>; Tue, 6 May 1997 12:13:12 -0500 (CDT)
Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id MAA14572 for <xemacs-beta@xemacs.org>; Tue, 6 May 1997 12:12:23 -0500 (CDT)
Received: from screamer.rtp.ericsson.se (screamer.rtp.ericsson.se [147.117.133.13]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with SMTP id MAA01134 for <xemacs-beta@xemacs.org>; Tue, 6 May 1997 12:12:22 -0500 (CDT)
Received: from rcur (rcur18.rtp.ericsson.se [147.117.133.138]) by screamer.rtp.ericsson.se (8.6.12/8.6.4) with ESMTP id NAA15226 for <xemacs-beta@xemacs.org>; Tue, 6 May 1997 13:12:21 -0400
To: XEmacs Beta Mailing List <xemacs-beta@xemacs.org>
Subject: Minibuffer and  multiple frames
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 06 May 1997 13:12:21 -0400
Message-ID: <16594.862938741@rtp.ericsson.se>
From: Raymond Toy <toy@rtp.ericsson.se>


I don't use multiple frames often, but I am beginning to use them a
bit more, and the following bugs me a lot

Consider the following, using 20.2-b4 on Solaris 2.5.1, with -q
-no-site-init.  Start up xemacs.  Make another frame.  In one frame 1,
do something like M-x gnuserv-start, but don't press return.  C-x o
cycles through the windows in this frame (*scratch* and the
minibuffer).  This is fine.

Now switch to frame 2.  The minibuffer contents now show up in frame
2.  However, C-x o in frame 2 won't cycle between the current window
and the minibuffer.  I can get to the minibuffer using the mouse,
though.

I find this annoying.  If the minibuffer is going to follow me around, 
I should be able to get to it using the same method in any frame.

Is this the desired/expected behaviour?  

Ray

