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.