From: martin rudalics <rudalics@gmx.at>
To: Gregory Heytings <gregory@heytings.org>
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 09:42:55 +0200 [thread overview]
Message-ID: <6f6e4aa5-9fdf-b4e6-04d5-c43448d67623@gmx.at> (raw)
In-Reply-To: <192e82f20f7e5133aaea@heytings.org>
> 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)?
For users (eq (current-buffer) (window-buffer)) _should_ be invariant.
When and if an application temporarily violates that invariant, it
should reestablish it before the user can see it. So if an application
calls `display-buffer' in a state where the invariant does not hold, it
should handle that case including the complication that `display-buffer'
might have selected another window. And it goes without saying that a
display buffer action should never violate that invariant.
martin
next prev parent reply other threads:[~2021-04-21 7:42 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
2021-04-21 7:42 ` martin rudalics [this message]
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=6f6e4aa5-9fdf-b4e6-04d5-c43448d67623@gmx.at \
--to=rudalics@gmx.at \
--cc=47894@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=juri@linkov.net \
--cc=max.brieiev@gmail.com \
/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.