walk-windows

walk-windows

[Drew Adams]

Can someone please explain a little about the logic behind the treatment of
a standalone minibuffer frame in `walk-windows' (hence also
`count-windows')? Here's the doc string:

 Cycle through all visible windows, calling proc for each one.
 proc is called with a window as argument.

 Optional second arg minibuf t means count the minibuffer window even
 if not active.  minibuf nil or omitted means count the minibuffer iff
 it is active.  minibuf neither t nor nil means not to count the
 minibuffer even if it is active.

 Several frames may share a single minibuffer; if the minibuffer
 counts, all windows on all frames that share that minibuffer count
 too.  Therefore, if you are using a separate minibuffer frame
 and the minibuffer is active and minibuf says it counts,
 `walk-windows' includes the windows in the frame from which you
 entered the minibuffer, as well as the minibuffer window.

 all-frames is the optional third argument.
 all-frames nil or omitted means cycle within the frames as specified above.
 all-frames = `visible' means include windows on all visible frames.
 all-frames = 0 means include windows on all visible and iconified frames.
 all-frames = t means include windows on all frames including invisible
frames.
 If all-frames is a frame, it means include windows on that frame.
 Anything else means restrict to the selected frame.

The first two sentences in the third paragraph seem to conflict. The first
says that "if the minibuffer counts, all windows on all frames that share
that minibuffer count too." The next one says that (only) "the windows in
the frame from which you entered the minibuffer" count too, not all other
frames that share the standalone minibuffer. Which is correct? This is
important, because it determines the meaning of `all-frames' when it is nil,
because the doc string says, about that, "the frames as specified above".

Beyond this confusion, I don't understand why you would want to include
windows on another frame, if all-frames is nil.

RE: walk-windows

[Drew Adams]

> Can someone please explain a little about the logic behind the 
> treatment of a standalone minibuffer frame in `walk-windows'
> (hence also `count-windows')?
...
> The first two sentences in the third paragraph seem to conflict....
> Which is correct? This is important, because it determines the
> meaning of `all-frames' when it is nil, because the doc string
> says, about that, "the frames as specified above".
> 
> Beyond this confusion, I don't understand why you would want to
> include windows on another frame, if all-frames is nil.

Can anyone help here? See original post for more info.