Re: Stop frames stealing eachothers' minibuffers!

[Gregory Heytings]

> > > - Optionally, tie the frame where a minibuffer interaction was 
> > > initiated to that minibuffer and when the ensuing action is performed, 
> > > make that frame the selected one.
> >
> > Isn't this what minibuffer-follows-selected-frame t is supposed to do? 
> > (Except that the frame is not automatically selected.)
>
> With 'minibuffer-follows-selected-frame' non-nil, the remainder of 
> 'switch-to-buffer' simply runs on the frame where the prompt is answered 
> which is not necessarily the frame where C-x b was issued initially.

Yes, and this is not what it is supposed to do.  The NEWS item says "the 
effect of what you type in the minibuffer happens in the frame where the 
minibuffer was first activated, even if it moved to another frame."