From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Stop frames stealing eachothers' minibuffers! Date: Fri, 27 Nov 2020 10:02:46 +0000 Message-ID: References: <53833023-d959-07af-7611-aa2e0bdcc1bc@gmx.at> <0d14bfc4-8e8e-d3b9-e0e1-ee4bf2e6449d@gmx.at> <20201125210947.GB8228@ACM> <20201125215450.GC8228@ACM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37324"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Andrii Kolomoiets , emacs-devel@gnu.org, martin rudalics , enometh@meer.net, Stefan Monnier , Eli Zaretskii To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 27 11:03:49 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kiabV-0009Ze-BQ for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Nov 2020 11:03:49 +0100 Original-Received: from localhost ([::1]:37136 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kiabU-0002gS-Eo for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Nov 2020 05:03:48 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50084) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kiaae-0001xn-Cz for emacs-devel@gnu.org; Fri, 27 Nov 2020 05:02:56 -0500 Original-Received: from colin.muc.de ([193.149.48.1]:62597 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.90_1) (envelope-from ) id 1kiaab-0001Jx-0f for emacs-devel@gnu.org; Fri, 27 Nov 2020 05:02:56 -0500 Original-Received: (qmail 53205 invoked by uid 3782); 27 Nov 2020 10:02:47 -0000 Original-Received: from acm.muc.de (p4fe15c16.dip0.t-ipconnect.de [79.225.92.22]) by localhost.muc.de (tmda-ofmipd) with ESMTP; Fri, 27 Nov 2020 11:02:46 +0100 Original-Received: (qmail 5296 invoked by uid 1000); 27 Nov 2020 10:02:46 -0000 Content-Disposition: inline In-Reply-To: X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.1; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:259860 Archived-At: Hello, Gregory. On Wed, Nov 25, 2020 at 22:23:17 +0000, Gregory Heytings wrote: > >>> 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 > ;-) It seems somewhat indefinite _when_ the recursive minibuffer "is" entered on frame F2, relative to the other operations. > >> 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? In Emacs 27, emacs -Q, C-x 5 2, giving a two-frame setup. In F1, C-x b. C-x 5 o, moving to F2. C-r SPACE. Note that the open minibuffer remains on F1. Now type C-x 8 RET SPACE RET. This sucks the open minibuffer over to F2, despite the C-r operation having nothing to do with the suspended operation in the minibuffer. This is not good and has been/is in the process of being fixed for Emacs 28. > 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. More precisely, if we're talking about Emacs 28 with minibuffer-follows-selected-frame at its default of t, the C-x C-f minibuffer moves to F2 when F2 gets selected. The M-: then gives an error message in F2, or (when enable-recursive-minibuffers is t) opens a recursive minibuffer in F2. -- Alan Mackenzie (Nuremberg, Germany).