From xemacs-m  Mon Dec 23 07:49:46 1996
Received: from mgate.uni-hannover.de (mgate.uni-hannover.de [130.75.2.3])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with SMTP
	  id HAA20355 for <xemacs-beta@xemacs.org>; Mon, 23 Dec 1996 07:49:44 -0600 (CST)
Received: from helios (actually helios.tnt.uni-hannover.de) by mgate 
          with SMTP (PP); Mon, 23 Dec 1996 14:49:24 +0100
Received: from daedalus.tnt.uni-hannover.de by helios (SMI-8.6/SMI-SVR4) 
          id OAA05645; Mon, 23 Dec 1996 14:49:13 +0100
Received: by daedalus.tnt.uni-hannover.de (SMI-8.6/SMI-SVR4) id OAA29520;
          Mon, 23 Dec 1996 14:49:11 +0100
Date: Mon, 23 Dec 1996 14:49:11 +0100
Message-Id: <199612231349.OAA29520@daedalus.tnt.uni-hannover.de>
From: Heiko Muenkel <muenkel@tnt.uni-hannover.de>
To: steve@miranova.com
Cc: xemacs-beta@xemacs.org
Subject: Re: Bug in find-file-other-frame
In-Reply-To: <m27mmdaz1g.fsf@altair.xemacs.org>
References: <199612201507.QAA20781@daedalus.tnt.uni-hannover.de> <m27mmdaz1g.fsf@altair.xemacs.org>
X-Face: n}R'l6CHRf>pi&bj7[x0CW3:kmXm@1)7m+l*9[fp;-Ow4Xe~=5E;skf?2> 
        y]f{HzB|Q(\V9+y$PP~.4G[2n4W7{6Ilm[AMY9B:0kj.K_$-d%p4YIF*bX;=ADp6{ 
        HS@NEv9c.VII+9PgXHASx}K(jy^t=q%qzZ72q1e4E;O!$A$`&wgtLk"1%p.nC_G!] 
        4d1!+J4Q#YD_iXeEy`1x)d\r$1Qn\'23n|[8Y_xzuXJJ7W(EGqnzB]`]aq??;+z=) 
        DW~\'Vq&F'g%QU[Mv2:}nS>SdZFTEC2GsgB=Q,:~H<R5S[:ZN%B:s0;|v1x"Jb
Mime-Version: 1.0 (generated by tm-edit 7.90)
Content-Type: text/plain; charset=US-ASCII

>>>>> "sb" == Steven L Baur <steve@miranova.com> writes:

>>>>> "Heiko" == Heiko Muenkel <muenkel@tnt.uni-hannover.de> writes:
    Heiko> XEmacs 19.15 Beta 5:

    sb> Presumably you mean beta 4, since beta 5 isn't out yet?

Sorry, I mean beta 4.

    Heiko> Assume the following:
 
    Heiko> 1. The current frame is frame-1

    Heiko> 2. In frame-1 the file foo-1 is displayed

    Heiko> 3. Run the command `M-x find-file-other-frame' to load a
    Heiko> file foo-2 in a new frame frame-2.

    Heiko> What now happens depends on the position of the mouse
    Heiko> pointer. If the mouse pointer is after the frame creation
    Heiko> over the frame-2, then frame-1 is correctly displaying file
    Heiko> foo-1 and frame-2 the file foo-2.  But if the mouse pointer
    Heiko> is after the frame creation in frame-1, then the file foo-1
    Heiko> is displayed in frame-2 and file foo-2 is displayed in
    Heiko> frame-1 and that is a bug. It's realy annoying, if frame-1
    Heiko> has multiple windows and one had used `M-x
    Heiko> find-file-other-frame' to retain the window configuration
    Heiko> of frame-1.

    sb> I agree that this sounds annoying.  What options are you
    sb> using?  I made a code change in this area for beta 3, (but not
    sb> beta 4) and it involved addition of the boolean variable
    sb> `focus-follows-mouse'.  There should not have been any change
    sb> when that variable is nil.

    sb> I cannot duplicate your results with `focus-follows-mouse' set
    sb> (and the X Window manager in focus follows mouse).

    sb> If you have `focus-follows-mouse' set, but your window manager
    sb> is click to type, turn off `focus-follows-mouse'.  --

I've now also problems to duplicate my results (sorry, it may be, that
I've mixed the behaviour of the 19.15 with the one of 19.14).

But however, in the 19.14 Beta 4 I'm seeing this annoying results
only if foo-2 is a directory, regardless of the position of the mouse
pointer and the value of `focus-follows-mouse'.  

My X Window manager has the focus follows mouse feature enabled.


