Re: Usage examples of dedicated windows and popup frames?

[martin rudalics <rudalics@gmx.at>]

 > However, `other-frame' raises and selects correctly.

Does `pop-to-buffer-other-frame' raise and select correctly when the
buffer argument is already shown on an iconified frame?

 >> Maybe we could make the *Completions* frame (optionally) invisible
 >> instead of iconfying it?
 >
 > What's "invisible" in this respect?  (In any case, I'd try it out.)

Hmm, invisible is invisible, see section 28.10 of the Elisp manual.
That is, we could make the frame optionally invisible and make it
visible again when it's needed.  For example, when I evaluate the
following three forms step by step

(setq my-frame (make-frame))

(make-frame-invisible my-frame)

(make-frame-visible my-frame)

my-frame is visible and has input focus after the third step.  If I do

(let ((frame (selected-frame)))
   (make-frame-visible my-frame)
   (raise-frame frame))

as third step, the original frame is in the foreground, and if I do

(let ((frame (selected-frame)))
   (make-frame-visible my-frame)
   (redirect-frame-focus my-frame frame))

as third step, my-frame is risen but typing input goes to the original
frame.  So there's a lot to experiment with for *Completions* and I'd
invite people to try out what works for them and their window managers.

martin