From: Gregory Heytings <gregory@heytings.org>
To: martin rudalics <rudalics@gmx.at>
Cc: max.brieiev@gmail.com, 47894@debbugs.gnu.org,
Juri Linkov <juri@linkov.net>
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 [thread overview]
Message-ID: <192e82f20f7e5133aaea@heytings.org> (raw)
In-Reply-To: <b3fe3e61-9446-c99f-fbe2-ccee3d75e850@gmx.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)?
next prev parent reply other threads:[~2021-04-21 7:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 16:06 bug#47894: 28.0.50; y.oy max.brieiev
2021-04-19 16:31 ` bug#47894: 28.0.50; isearch does not work if enable-recursive-minibuffers is on and some input method is set max.brieiev
2021-04-19 20:49 ` Juri Linkov
2021-04-20 20:00 ` Juri Linkov
2021-04-20 20:15 ` Gregory Heytings
2021-04-20 21:51 ` Gregory Heytings
2021-04-20 22:35 ` Gregory Heytings
2021-04-21 6:21 ` Gregory Heytings
2021-04-21 7:03 ` martin rudalics
2021-04-21 7:16 ` Gregory Heytings [this message]
2021-04-21 7:42 ` martin rudalics
2021-04-21 7:49 ` Gregory Heytings
2021-04-21 17:02 ` Juri Linkov
2021-04-21 17:18 ` Gregory Heytings
2021-04-21 17:37 ` Juri Linkov
2021-04-21 17:59 ` Juri Linkov
2021-04-21 19:23 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=192e82f20f7e5133aaea@heytings.org \
--to=gregory@heytings.org \
--cc=47894@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=max.brieiev@gmail.com \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.