From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: New multi-command facility displays in the wrong echo area. Date: Sat, 10 Oct 2020 09:44:16 -0400 Message-ID: References: <20201009163445.GB4027@ACM> <20201010101509.GA5662@ACM> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23593"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Gregory Heytings , emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 10 15:45:17 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 1kRFBU-00061m-IQ for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 15:45:16 +0200 Original-Received: from localhost ([::1]:39336 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kRFBT-0005OL-IV for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 09:45:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38202) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kRFAc-0004uF-Rq for emacs-devel@gnu.org; Sat, 10 Oct 2020 09:44:23 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:40814) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kRFAZ-0002oL-Jp for emacs-devel@gnu.org; Sat, 10 Oct 2020 09:44:21 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id BC89B440F7D; Sat, 10 Oct 2020 09:44:18 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 7C518440F7A; Sat, 10 Oct 2020 09:44:17 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1602337457; bh=5s6U/3ll/0fUeTxDN7z13kpqxztY3/sNlTGRTU9ejOk=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Q3/GsXWqyLO9E5f5VjsYVtF8X84RbHazf0wJdPORwRj4KEFpqCLWcQfN9a2khlumm IIIIAFCZ26/yq/PlSGOYj+rtYqJaHS1Kw/dYCadZLirkpqIVb0JxH7KUb0tnKs7oPS /i7nUP9MErg8rFiMwtSQLbwTSL0vEcg8S7K0BW5eAN0iBFZM19Hp1gCcCsjOYsjGkM mv1sN6cyRaP7mwVeeKEEvtrmutoU4rfTKT/zcdL6pWpK3UDS/t0jYmK/A8y7v70vHv PW3pOOsjPtyYnLyL6jfNnYWpTU/Xr7zo/rxNfZF2pET3ubgzBVGVdlaa4p7Vcv4Lxo sEVgJ5B94OuBA== Original-Received: from alfajor (unknown [157.52.9.240]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4F3C1120117; Sat, 10 Oct 2020 09:44:17 -0400 (EDT) In-Reply-To: <20201010101509.GA5662@ACM> (Alan Mackenzie's message of "Sat, 10 Oct 2020 10:15:09 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/10 09:40:07 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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:257325 Archived-At: >> (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. Indeed. It looks like I misremembered! This looks like a plain bug fix that should be on `emacs-27`. Thanks, Stefan