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: Fri, 27 Nov 2020 17:03:49 +0200 Message-ID: <83tutaon8q.fsf@gnu.org> References: <53833023-d959-07af-7611-aa2e0bdcc1bc@gmx.at> <0d14bfc4-8e8e-d3b9-e0e1-ee4bf2e6449d@gmx.at> <20201125210947.GB8228@ACM> <835z5roud4.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16202"; mail-complaints-to="usenet@ciao.gmane.io" Cc: andreyk.mad@gmail.com, emacs-devel@gnu.org, rudalics@gmx.at, enometh@meer.net, monnier@iro.umontreal.ca, acm@muc.de To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 27 16:33:29 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 1kifkX-000456-3k for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Nov 2020 16:33:29 +0100 Original-Received: from localhost ([::1]:55590 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kifkW-0005tr-5y for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Nov 2020 10:33:28 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40912) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kifIB-0006ep-NU for emacs-devel@gnu.org; Fri, 27 Nov 2020 10:04:11 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51738) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kifI8-0000xM-4j; Fri, 27 Nov 2020 10:04:08 -0500 Original-Received: from [176.228.60.248] (port=3369 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kifI7-000265-Eo; Fri, 27 Nov 2020 10:04:07 -0500 In-Reply-To: (message from Gregory Heytings on Fri, 27 Nov 2020 13:43:27 +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:259897 Archived-At: > Date: Fri, 27 Nov 2020 13:43:27 +0000 > From: Gregory Heytings > cc: martin rudalics , andreyk.mad@gmail.com, > emacs-devel@gnu.org, enometh@meer.net, monnier@iro.umontreal.ca, > acm@muc.de > > >> Having a customizable variable like 'minibuffer-follows-selected-frame' > >> whose purpose is to get back the old behavior, should also provide that > >> old behavior as faithfully as possible IMHO. > > > > The NEWS entry clearly says that the old behavior is no longer > > available, so getting back the old behavior is not the purpose of that > > variable. > > I hope that does not mean "end of discussion". No, it's just to point out that Martin was expecting from that variable something it didn't intend to provide. > it is surprising that such a radical change was accepted without > testing these cases, which are obvious cases to test. The master branch _is_ for testing things. If a change has adverse effects, those adverse effects should be fixed. If it turns out there are too many adverse effects that cannot be reasonably fixed, the change will be reverted. > The NEWS entry says "Nevertheless, the effect of what you type in the > minibuffer happens in the frame where the minibuffer was first activated, > even if it moved to another frame." This is not correct. Three recipes: Please report bugs about these recipes, they need to be investigated, and either they or the documentation needs to be fixed. TIA