RE: switch-to-buffer-other-frame fails to pop-up window

["Drew Adams" <drew.adams@oracle.com>]

> > There are thus different use cases and preferences.
>
> do you think it is worth while to catalog the styles of use?  as
> a prelude to finding a way to better support them?

I wouldn't try, but that's sort of what happens anyway, little by little.
When someone such as Martin tries to fix a reported bug, he tries to
understand the reported use case and accomodate it appropriately.

> i want a separate help buffer per frame without having to
> rename it by hand.  i tried to do that by hooking help-mode.el's
> "help-buffer" function (which computes the appropriate help buffer
> name) but i could not get it to discover the containing frame object.
>
> by the time 'help-buffer' was called, the magic minibuffer
> implementation arranged for the magic minibuffer frame (not a
> dedicated minibuffer frame like the one you use but probably a magic
> one to allow sharing of the minibuffer across different real buffer
> frames) to be the 'selected-frame'.
>
> you can see this by doing "M-: (selected-frame)' after a fresh "emacs
> -Q" and then repeating after popping up a second frame.  once you've
> popped up a second frame, '(selected-frame)' under "M-:" always
> returns the magic minibuffer frame (which i think is a bug).

No, if I understand you correctly, that is normal. During `M-:', the
minibuffer must have the input focus, so its frame is selected.