From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: New multi-command facility displays in the wrong echo area. Date: Sat, 10 Oct 2020 20:20:07 +0000 Message-ID: References: <20201009163445.GB4027@ACM> <20201009203810.GC4027@ACM> <83imbi609a.fsf@gnu.org> <20201010103233.GB5662@ACM> <834kn25o6b.fsf@gnu.org> <20201010124446.GC5662@ACM> <20201010134727.GD5662@ACM> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="-212064758-2146600384-1602359487=:21577" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18128"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Eli Zaretskii , 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 22:21:15 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 1kRLMh-0004bO-NJ for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 22:21:15 +0200 Original-Received: from localhost ([::1]:39010 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kRLMg-000708-NV for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 16:21:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48084) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kRLLn-0006VL-Gz for emacs-devel@gnu.org; Sat, 10 Oct 2020 16:20:19 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:52042) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kRLLl-0004cJ-Eo; Sat, 10 Oct 2020 16:20:19 -0400 Original-Received: from sdf.org (IDENT:ghe@otaku.sdf.org [205.166.94.8]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 09AKKA9C024970 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Sat, 10 Oct 2020 20:20:10 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 09AKKWfN005241; Sat, 10 Oct 2020 20:20:32 GMT In-Reply-To: <20201010134727.GD5662@ACM> Content-ID: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/10 16:20:13 X-ACL-Warn: Detected OS = ??? 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_PASS=-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:257333 Archived-At: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---212064758-2146600384-1602359487=:21577 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: Hi Alan, >>>> Yet another similar use case is when you type "C-x 8 RET" during=20 >>>> Isearch: that reads the character's name/codepoint from the=20 >>>> minibuffer. >>> >>> This goes wrong. With C-x b active on frame F1, move to F2, start an= =20 >>> isearch, C-x 8 RET, use TAB completion to select a character and RET.= =20 >>> This displays >>> >>> Switch to buffer (default xdisp.c): [Failing I-search: su=EF=BF=BD] >>> >>> on F2. On terminating the isearch and completing the C-x b action in= =20 >>> F2's minibufer, the buffer switch has worked in frame F1. >> >> It doesn't go wrong, it has moved the minibuffer from frame F1 to frame= =20 >> F2. > > The minibuffer's contents, the C-x b, is acting on F1. It is surely=20 > wrong to have moved the minibuffer to F2. > It can perhaps be argued that it is wrong, but it's a different problem,=20 and this behavior exists since Emacs 24. FWIW, I don't think it is wrong: the minibuffer has indeed moved to F2,=20 but when you press RET after choosing the buffer you want, the buffer=20 switch happens in F1. And on a TTY, Emacs even goes back to F1. ---212064758-2146600384-1602359487=:21577--