From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Stop frames stealing eachothers' minibuffers! Date: Thu, 15 Oct 2020 16:44:42 +0300 Message-ID: <83sgafy56d.fsf@gnu.org> References: <20201013195103.GB8896@ACM> <20201013204408.GC8896@ACM> <831ri027vz.fsf@gnu.org> <20201014160240.GA7651@ACM> <83d01kzswk.fsf@gnu.org> <20201014163534.GB7651@ACM> <838sc8zqjj.fsf@gnu.org> <20201014184523.GC7651@ACM> <83y2k8y6qs.fsf@gnu.org> <20201014194904.GD7651@ACM> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22966"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ghe@sdf.org, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 15 16:01:36 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 1kT3p2-0005sT-84 for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Oct 2020 16:01:36 +0200 Original-Received: from localhost ([::1]:42364 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kT3p1-0004Lh-9x for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Oct 2020 10:01:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53532) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kT3YX-0001x9-1Y for emacs-devel@gnu.org; Thu, 15 Oct 2020 09:44:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50602) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kT3YT-00015x-Tb; Thu, 15 Oct 2020 09:44:29 -0400 Original-Received: from [176.228.60.248] (port=1141 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kT3YS-0003Lh-OK; Thu, 15 Oct 2020 09:44:29 -0400 In-Reply-To: <20201014194904.GD7651@ACM> (message from Alan Mackenzie on Wed, 14 Oct 2020 19:49:04 +0000) 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:257728 Archived-At: > Date: Wed, 14 Oct 2020 19:49:04 +0000 > Cc: ghe@sdf.org, emacs-devel@gnu.org > From: Alan Mackenzie > > > > Starting again from a vanilla state: > > > (iv) On F1, C-x b ; Leaves a minibuffer open. > > > (v) Move to F2. > > > (vi) C-s foo ; Leaves an Isearch active. > > > (vii) C-x 8 RET RET ; Inserts a foreign character into > > > the search string. > > > (viii) RET ; Terminates Isearch. > > > > On the current master, the minibuffer has been moved to F2. With my > > > patch, it would still be on F1. With the "always" variation it would be > > > on F2 (or, possibly on all frames). > > > You should try this with the emacs-27 branch, because Gregory's patch > > installed there (and will be soon merged to master) changes the > > behavior quite a bit. > > I've just tried it. The behaviour is indeed that which I noted above - > the minibuffer moves to F2 if and only if a minibuffer has been used in > Isearch. > > > > The current master seems to me to be inconsistent, in that whether the > > > minibuffer moves from F1 to F2 depends on whether the Isearch used a > > > (recursive) minibuffer. > > > AFAICT, this no longer happens. > > Oh, but it does. We are talking past each other. This behavior of the current emacs-27 branchlooks correct to me: On F1, C-x b Move to F2 C-s foo ; Isearch prompt appears in F2's echo area C-x 8 RET RET; editing is in F2's minibuffer RET ; terminates Isearch and leaves the active minibuffer on F2 This behavior is wrong: On F1, C-x b Move to F2 C-s foo ; Isearch prompt appears in F2's echo area RET ; terminates Isearch and leaves the active minibuffer on F1 The latter is correct, except for the last step: the active minibuffer should have switched to F2, which is now the selected frame. > > > With my patch, a minibuffer would remain on the frame it was opened on, > > > no matter what. > > > That's a separate issue, I believe. I'm not sure I like the behavior > > you suggest. If the user switched to a different frame, why should > > the minibuffer prompt stay on the non-selected frame? > > Because the action which the minibuffer will invoke usually takes place > in that now non-selected frame. There's no guarantee of that. Moreover, a non-selected frame could have been iconified or even deleted. The only sane place to continue interaction is on the selected frame (and let's leave the use case of separate minibuffer-only frame aside, okay?). > I feel a bit of a jolt when I hit RET in F2, but the effect (of > switch-to-buffer) takes place in F1. This applies to C-x C-f, C-x > C-w, C-x b, M-x imenu, ..... Not clear why: you switched to another frame, so continue using that. If you want to continue using the original frame, switch back there.