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: New multi-command facility displays in the wrong echo area. Date: Sat, 10 Oct 2020 14:13:32 +0300 Message-ID: <834kn25o6b.fsf@gnu.org> References: <20201009163445.GB4027@ACM> <20201009203810.GC4027@ACM> <83imbi609a.fsf@gnu.org> <20201010103233.GB5662@ACM> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8494"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, 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 13:14:24 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 1kRCpT-00026o-Ul for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 13:14:23 +0200 Original-Received: from localhost ([::1]:40814 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kRCpT-0007n1-13 for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 07:14:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46370) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kRCog-0007Lh-40 for emacs-devel@gnu.org; Sat, 10 Oct 2020 07:13:34 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35587) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kRCoe-0003k1-LG; Sat, 10 Oct 2020 07:13:32 -0400 Original-Received: from [176.228.60.248] (port=1883 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kRCoe-0002I1-2y; Sat, 10 Oct 2020 07:13:32 -0400 In-Reply-To: <20201010103233.GB5662@ACM> (message from Alan Mackenzie on Sat, 10 Oct 2020 10:32:33 +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:257317 Archived-At: > Date: Sat, 10 Oct 2020 10:32:33 +0000 > From: Alan Mackenzie > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > > > Do you intend to leave the active minibuffer on the original frame, and > > use the other frame for Isearch? Note that Isearch also uses the > > minibuffer. > > I'm not understanding that, properly. When I enter characters into > isearch in F2, this doesn't throw an error when the F1 minibuffer is > still active. Is isearch perhaps just using the echo area, here? > > Anyway, I tried the suggestion of Gregory Heytings from yesterday evening > at 21:48:49 +0000. He put an extra condition into > set-minibuffer-message, so that it only does its thing when the current > frame is also the minibuffer's frame. It appears to work well. Does that work if you set tty-menu-open-use-tmm non-nil, then press f10 while the I-search: prompt is active? This is one case where Isearch reads from the minibuffer. Another, perhaps more important, use case is when you type "M-s e" during Isearch: that enters the minibuffer to let you edit the search string. Yet another similar use case is when you type "C-x 8 RET" during Isearch: that reads the character's name/codepoint from the minibuffer. These are the use cases I had in mind when I asked about Isearch using the minibuffer.