From xemacs-m  Mon Mar 24 06:29:06 1997
Received: from frege.math.ethz.ch (root@frege-d-math-north-g-west.math.ethz.ch [129.132.145.3])
	by xemacs.org (8.8.5/8.8.5) with SMTP id GAA04738
	for <xemacs-beta@xemacs.org>; Mon, 24 Mar 1997 06:29:02 -0600 (CST)
Received: from fresnel.math.ethz.ch (vroonhof@fresnel [129.132.145.6]) by frege.math.ethz.ch (8.6.12/Main-STAT-mailer) with ESMTP id NAA22967 for <xemacs-beta@xemacs.org>; Mon, 24 Mar 1997 13:28:30 +0100
Received: (vroonhof@localhost) by fresnel.math.ethz.ch (8.6.9/D-MATH-client) id NAA20617; Mon, 24 Mar 1997 13:25:17 +0100
Sender: vroonhof@math.ethz.ch
To: xemacs-beta@xemacs.org
Subject: Re: other-frame
References: <9703240209.AA12448@GS213.SP.CS.CMU.EDU>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Date: 24 Mar 1997 13:25:16 +0100
In-Reply-To: Darrell Kindred's message of Sun, 23 Mar 1997 21:09:16 -0500
Message-ID: <byhgi1a34j.fsf@math.ethz.ch>
Lines: 38
X-Mailer: Gnus v5.4.33/XEmacs 19.15(beta103)

Darrell Kindred <dkindred@cmu.edu> writes:

> The other-frame function (C-x 5 o) cycles through hidden
> frames (in other fvwm pages), since it calls next-frame
> with 'visible-nomini.  Wasn't part of the point of updating
> the visibility flag for such frames that `C-x 5 o' could
> ignore them?

I thought about but couldn't decide about what to do it. I was a bit
afraid (and too lazy to add yet another case to the ugly ifs in the
next-frame c-code.)

> It seems to me that we should do one of these
> two things:
> 
>   1. change other-frame to ignore hidden frames (which will
>      require adding yet another option to next-frame, maybe
>      'visible-nohidden-nomini).

May be it is time to let next-frame take a list of required properties
instead of the new symbols?

>   2. do whatever it is that FSF does to cause fvwm to switch
>      to the appropriate page when selecting a frame that's
>      hidden. 

FVWM switches to right page.. that would be nice. Are you sure FSF
doesn't just do a 'raise' and/or grasp focus and you have some cool
fvwm setup to do the switch... (Here a raise makes the frame appear on
the local page :-(). I don't have the FSF sources handy to check.

> 
> I think I'd prefer #1.

Add a new variable that controls the behaviour and make #1 the
default.

Jan

