From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#47894: 28.0.50; isearch does not work if enable-recursive-minibuffers is on and some input method is set. Date: Wed, 21 Apr 2021 07:16:31 +0000 Message-ID: <192e82f20f7e5133aaea@heytings.org> References: <87eef6p8bh.fsf@gmail.com> <874kg0d8ui.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39874"; mail-complaints-to="usenet@ciao.gmane.io" Cc: max.brieiev@gmail.com, 47894@debbugs.gnu.org, Juri Linkov To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Apr 21 09:17:11 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1lZ76l-000AG9-LI for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 21 Apr 2021 09:17:11 +0200 Original-Received: from localhost ([::1]:45686 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lZ76k-00078P-A0 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 21 Apr 2021 03:17:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42748) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lZ76c-00077w-K1 for bug-gnu-emacs@gnu.org; Wed, 21 Apr 2021 03:17:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45297) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lZ76b-00066U-Rp for bug-gnu-emacs@gnu.org; Wed, 21 Apr 2021 03:17:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lZ76b-0001b5-L8; Wed, 21 Apr 2021 03:17:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org, bugs@gnus.org Resent-Date: Wed, 21 Apr 2021 07:17:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47894 X-GNU-PR-Package: emacs,gnus Original-Received: via spool by 47894-submit@debbugs.gnu.org id=B47894.16189893956096 (code B ref 47894); Wed, 21 Apr 2021 07:17:01 +0000 Original-Received: (at 47894) by debbugs.gnu.org; 21 Apr 2021 07:16:35 +0000 Original-Received: from localhost ([127.0.0.1]:56841 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lZ76A-0001aG-VN for submit@debbugs.gnu.org; Wed, 21 Apr 2021 03:16:35 -0400 Original-Received: from heytings.org ([95.142.160.155]:46928) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lZ768-0001a6-HZ for 47894@debbugs.gnu.org; Wed, 21 Apr 2021 03:16:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1618989391; bh=uFoXhYkz5a32q7oi6vnLuxbg8f59XYbYgbzLSw3v9/8=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=MzAxrW9NRSWGfmZn5PY2WhYZg2QKZqLaC8PJkCf8rwaovnrZpAdMapuWMZUh2Qya+ VYqSIvaK8x7NgO3oXIRC+KZhH1XC+Gs4nM15Fn4rpySLXvapJYKnh1OSL6eu03EIKP d6fSZ3iU9ZBhtjkwTpHFjE7W90FRfVl5yZlK5xuLg1DR5/oZOpnvBMBjJZsBBgldkC kLqOIzrC/fzy3tvTPF5gGZPjJZog7HiECg7VCW+37SwpGnFKj4Iy7BSTWwjl7La+t9 HeFJLJ7ONYm+QfgF6RraG9EU3nEdSPd8l5OajWQGouVbqlmahWvKOeohpROp4CkZTw FVROzrvOlZhqQ== In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:204580 Archived-At: >> - display-buffer-select is not a documented action, and does not even >> appear in the sources (even Google does not find it!), yet it works; > > I don't understand you here. It is defined above > Yes, I guess I was a bit tired when I wrote this ;-) Sorry for the noise. >> - After this action, point has moved, but (current-buffer) does not >> return the buffer where point is; (window-buffer (selected-window)) >> does. It seems to me that at the top-level these two should always be >> equal; apparently they are not. > > They need not be equal - only command_loop_1 ascertains that once here > > /* Make sure the current window's buffer is selected. */ > set_buffer_internal (XBUFFER (XWINDOW (selected_window)->contents)); > > but `display-buffer' can be called anywhere. The major point is that, > due to the fact that `display-buffer' may pop up a new frame and the WM > will usually focus that frame, an application can _never_ be sure which > window will get selected and which buffer will be current after calling > `display-buffer' finished. > Okay, thanks for the clarification. IIUC the right way to determine what the "current buffer" is (from a user's point of view: in which buffer will "a" be added if I press "a") is what I do: (window-buffer (selected-window)) and not what I did: (current-buffer)?