Re: Stop frames stealing eachothers' minibuffers!

[martin rudalics]

> My feeling (I did not look at the code) is that too many things were
> changed at once.  Perhaps this should be done / have been done in two
> steps, first implement the additional behavior 2, then behavior 3.

There are two things we could consider with
'minibuffer-follows-selected-frame' non-nil:

- Optionally, don't move the minibuffer window too eagerly.  Moving the
  prompt to my separate *Info* frame that I just want to consult for the
  interaction I'm about to perform might look gratuitous.

- 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.

But I think the main task for the moment is to fix the
'minibuffer-follows-selected-frame' nil behavior.

martin