From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 44070@debbugs.gnu.org
Subject: bug#44070: 28.0.50; Minibuffer display "jumps" upon minor edit
Date: Sun, 01 Nov 2020 17:45:28 +0200 [thread overview]
Message-ID: <83lfflf5d3.fsf@gnu.org> (raw)
In-Reply-To: <jwv7dr52im8.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 01 Nov 2020 10:38:03 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 44070@debbugs.gnu.org
> Date: Sun, 01 Nov 2020 10:38:03 -0500
>
> > I thought about testing equality between the window being redisplayed
> > and minibuf_window. We could also look at the buffer displayed by the
> > window, and see if it appears in Vminibuffer_list. Does that make
> > sense?
>
> Sounds pretty ugly.
??? Why? In any case, we do this stuff all over the place. A random
example:
else if ((w != XWINDOW (minibuf_window)
|| minibuf_level == 0)
/* When buffer is nonempty, redisplay window normally. */
&& BUF_Z (XBUFFER (w->contents)) == BUF_BEG (XBUFFER (w->contents))
/* Quail displays non-mini buffers in minibuffer window.
In that case, redisplay the window normally. */
&& !NILP (Fmemq (w->contents, Vminibuffer_list)))
prev parent reply other threads:[~2020-11-01 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 22:09 bug#44070: 28.0.50; Minibuffer display "jumps" upon minor edit Stefan Monnier
2020-10-19 16:34 ` Eli Zaretskii
2020-10-29 17:54 ` Stefan Monnier
2020-10-31 8:35 ` Eli Zaretskii
2020-10-31 13:12 ` Stefan Monnier
2020-10-31 18:40 ` Eli Zaretskii
2020-11-01 13:29 ` Stefan Monnier
2020-11-01 14:12 ` Stefan Monnier
2020-11-01 15:38 ` Eli Zaretskii
2020-11-01 18:59 ` Stefan Monnier
2020-11-01 19:36 ` Eli Zaretskii
2020-11-01 19:54 ` Stefan Monnier
2020-11-01 15:32 ` Eli Zaretskii
2020-11-01 15:38 ` Stefan Monnier
2020-11-01 15:45 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lfflf5d3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44070@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).