Re: Stop frames stealing eachothers' minibuffers!

[Gregory Heytings]

> > Having a customizable variable like 'minibuffer-follows-selected-frame' 
> > whose purpose is to get back the old behavior, should also provide that 
> > old behavior as faithfully as possible IMHO.
>
> The NEWS entry clearly says that the old behavior is no longer 
> available, so getting back the old behavior is not the purpose of that 
> variable.

I hope that does not mean "end of discussion".

I sent two recipes to Martin a few hours ago, which demonstrate that the 
behavior with that variable set to nil is broken.  Again it is surprising 
that such a radical change was accepted without testing these cases, which 
are obvious cases to test.

The NEWS entry says "Nevertheless, 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."  This is not correct.  Three recipes:

emacs -Q
C-x 5 2
C-x C-f
C-x 5 o
C-x o
.emacs RET

The file is opened in the frame in which you are, not in the frame in 
which C-x C-f was entered.

Another recipe:

emacs -Q
C-x 5 2
C-h f setq
C-x 5 o
C-x o
RET

The *Help* buffer is displayed in the frame in which you are, not in the 
frame in which C-h f setq was entered.

Yet another recipe, similar to the one with which this discussion started:

emacs -Q
C-x 5 2
C-x b
C-x 5 o
C-x o
RET

The buffer is displayed in the frame in which you are, not in the frame in 
which C-x b was entered.