|
From: | Gregory Heytings |
Subject: | Re: Stop frames stealing eachothers' minibuffers! |
Date: | Wed, 25 Nov 2020 22:23:17 +0000 |
User-agent: | Alpine 2.22 (NEB 394 2020-01-19) |
The behaviour in Emacs 27 is chaotic. Sometimes a minibuffer moves with a frame switch, sometimes it doesn't.I wouldn't write it is "chaotic". The behavior you consider "chaotic" is well-defined, and has been there since Emacs 21 at least: the minibuffer moves from frame F1 to frame F2 if and only if the minibuffer is active on frame F1 and a recursive minibuffer is entered on frame F2.I'm not sure what you mean by "is" in that sentence.
I've reread what I wrote five times, and I don't understand the question ;-)
There are other possible behaviors of course, but IMO the current one is a reasonable one.If a recursive minibuffer operation has been carried out, then the minibuffer moves, if it hasn't it doesn't. That means Emacs has some invisible internal state, something which doesn't seem desirable.
What do you mean? By definition a recursive minibuffer is entered when a minibuffer has been entered and not yet left, that is, when the operation has not yet been completed. After typing C-x C-f in frame F1 and M-: in frame F2, the two minibuffers have been moved to frame F2.
[Prev in Thread] | Current Thread | [Next in Thread] |