Re: Stop frames stealing eachothers' minibuffers!

[martin rudalics]

>> If, with Emacs 28, I set 'minibuffer-follows-selected-frame' to non-nil,
>
> Do you mean "to nil", here?  That variable is non-nil by default.

Right.  I meant "to nil" here.

>> the behavior does not entirely match that of Emacs 27 because the second
>> RET must be typed in the first frame.  So if some application relies on
>> the exact replication of the behavior of Emacs 27, we have a regression.
>
> Well the new behaviour is explicitly not wholly compatible with the old.
> I'm not sure that counts as a regression.

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.

martin