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 21:18:10 +0300 Message-ID: <83wnzrwdy5.fsf@gnu.org> References: <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> <83sgafy56d.fsf@gnu.org> <20201015180143.GA10229@ACM> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38404"; 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 20:37:26 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 1kT87y-0009uW-BO for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Oct 2020 20:37:26 +0200 Original-Received: from localhost ([::1]:36810 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kT87x-0004IM-BY for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Oct 2020 14:37:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36050) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kT7pX-0004kW-BQ for emacs-devel@gnu.org; Thu, 15 Oct 2020 14:18:23 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55788) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kT7pU-0003mL-Ud; Thu, 15 Oct 2020 14:18:21 -0400 Original-Received: from [176.228.60.248] (port=2469 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kT7pO-00021I-46; Thu, 15 Oct 2020 14:18:18 -0400 In-Reply-To: <20201015180143.GA10229@ACM> (message from Alan Mackenzie on Thu, 15 Oct 2020 18:01:43 +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:257755 Archived-At: > Date: Thu, 15 Oct 2020 18:01:43 +0000 > Cc: ghe@sdf.org, emacs-devel@gnu.org > From: Alan Mackenzie > > > The latter is correct, except for the last step: the active minibuffer > > should have switched to F2, which is now the selected frame. > > OK, but I disagree. We seem to have different mental models of the > minibuffer. For you, the MB, I think, is what demands immediate > attention, therefore should be on the selected frame. For me, the MB is > an integral part of the frame on which it was opened. > > Is there any chance we could implement an option for this (which has been > mentioned already)? I'm okay with such an option. I think I already said that. > > > 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. > > The problem happens to me when I've forgotten I've still got an open > minibuffer on the other frame. The frame's title will help, as it shows "*Minibuf-1*" or somesuch. > Anyhow, back to practicalities. I think we agreed last night (talking > about the "hybrid" option) that the current way of doing things isn't > very good. I think, but I'm not sure, that you're saying the MB, if > open, should always be present on the currently selected frame and > nowhere else. If I'm wrong here, could you possibly give a precise > description of when you say the MB should be moved to a different frame. IMO, the minibuffer should _always_ be on the selected frame, unless it has its own minibuffer-only frame (in which case it is always there).