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: New multi-command facility displays in the wrong echo area. Date: Sat, 10 Oct 2020 10:15:09 +0000 Message-ID: <20201010101509.GA5662@ACM> References: <20201009163445.GB4027@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="6935"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 10 12:24:23 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 1kRC35-0001jP-9a for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 12:24:23 +0200 Original-Received: from localhost ([::1]:38336 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kRC34-0000gS-Cd for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 06:24:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34846) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kRBuH-0002cC-5A for emacs-devel@gnu.org; Sat, 10 Oct 2020 06:15:17 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:21114 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.90_1) (envelope-from ) id 1kRBuC-00052Y-MS for emacs-devel@gnu.org; Sat, 10 Oct 2020 06:15:15 -0400 Original-Received: (qmail 36784 invoked by uid 3782); 10 Oct 2020 10:15:10 -0000 Original-Received: from acm.muc.de (p2e5d5308.dip0.t-ipconnect.de [46.93.83.8]) by localhost.muc.de (tmda-ofmipd) with ESMTP; Sat, 10 Oct 2020 12:15:09 +0200 Original-Received: (qmail 5686 invoked by uid 1000); 10 Oct 2020 10:15:09 -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-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/10 06:15:10 X-ACL-Warn: Detected OS = FreeBSD 9.x or newer [fuzzy] 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=ham 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:257312 Archived-At: Hello, Gregory. On Fri, Oct 09, 2020 at 21:48:49 +0000, Gregory Heytings wrote: > Hi Stefan, > >>> (i) In a GUI environment, create two frames, each displaying a buffer. > >>> (ii) In frame F1, do C-x b `switch-to-buffer', but don't type anything more. > >>> (iii) Move to frame F2, and start an isearch with C-s some-text. > >>> Although currently in F2, the isearch's pattern is displayed in the > >>> echo area for F1. This is wrong. > >> FWIW, this behavior has been with us at least since Emacs-21. > > I fear that's not correct. I don't see this behavior in Emacs 21 to 26 > > (inclusive), it is new in Emacs 27.1. More precisely, it is because the > > new variable set-message-function has the default value > > set-minibuffer-message. To restore the previous default behavior: > > (setq set-message-function nil) > IMO this could/should be fixed in set-minibuffer-message, by checking that > the active minibuffer is on the same frame: > (when (and (not noninteractive) > (window-live-p (active-minibuffer-window)) > (eq (window-frame) (window-frame (active-minibuffer-window))) Thanks! I've just tried this out, and it appears to work well. In particular, in the scenario I outlined, on a TTY, the echo area for frame F2 is used when F2 is the current frame, even if there is a minibuffer active in F1. -- Alan Mackenzie (Nuremberg, Germany).