Re: Stop frames stealing eachothers' minibuffers!

[Stefan Monnier]

>> Seeing as how a minibuffer often has a strong association with its frame
>> (e.g., C-x C-f opens a buffer in the same frame it was invoked from),
>> this shifting of minibuffers from one frame to another is confusing.
> Is it?  It makes sure the minibuffer is on the selected frame, which
> is natural in many/most use cases.

But it only makes sure after you used another minibuffer, so in the
remaining 90% of the cases you're still left with an active minibuffer
that is not on the selected frame.

If that 90% is not considered a problem, then I wonder what's different
after using a nested minibuffer to justify the current behavior?


        Stefan