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, 22 Oct 2020 19:14:09 +0300 Message-ID: <83h7qmkzla.fsf@gnu.org> References: <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> <83wnzrwdy5.fsf@gnu.org> <20201021151945.GA19276@ACM> <20201021200438.GF19276@ACM> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40029"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 22 18:15:16 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 1kVdFD-000AEj-U9 for ged-emacs-devel@m.gmane-mx.org; Thu, 22 Oct 2020 18:15:15 +0200 Original-Received: from localhost ([::1]:33554 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kVdFC-0002H4-Uj for ged-emacs-devel@m.gmane-mx.org; Thu, 22 Oct 2020 12:15:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50670) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kVdDw-0001nv-DC for emacs-devel@gnu.org; Thu, 22 Oct 2020 12:13:57 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46642) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kVdDv-0002s6-OU; Thu, 22 Oct 2020 12:13:55 -0400 Original-Received: from [176.228.60.248] (port=1261 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kVdDu-0003xX-NS; Thu, 22 Oct 2020 12:13:55 -0400 In-Reply-To: <20201021200438.GF19276@ACM> (message from Alan Mackenzie on Wed, 21 Oct 2020 20:04:38 +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:258308 Archived-At: > Date: Wed, 21 Oct 2020 20:04:38 +0000 > Cc: emacs-devel@gnu.org > From: Alan Mackenzie > > Here's a corrected version of the patch, incorporating fixes and > suggestions from Stefan and Drew: Thanks, I have a few minor comments: > +the user option @code{minibuffer-follows-frame} to @code{nil}, then I'd prefer to name the option minibuffer-follows-selected-frame. > ++++ > +** Switching frames when a minibuffer is active has been rationalized. "Rationalized"? How about Minibuffer behavior when selected frame changes can now be controlled. ? > +By default, the active minibuffer is moved to the newly selected > +frame. When the current command is continued (by completing the > +minibuffer action), it takes effect in the frame where the minibuffer > +was first opened. An alternative behavior is available by customizing > +'minibuffer-follows-frame' to nil. Here, the minibuffer stays in the > +frame where it was first opened, and you must switch back to this > +frame to continue or abort the current command. The old (pre Emacs > +28.1) somewhat unsystematic behavior is no longer available. Can you reword to use less of passive tense here? I may be missing something: where does this code handles the case of minibuffer-only frames?