From: Eli Zaretskii <eliz@gnu.org>
To: spacibba@aol.com
Cc: 54450@debbugs.gnu.org
Subject: bug#54450: 29.0.50; redisplay--pre-redisplay-functions issue
Date: Fri, 18 Mar 2022 20:54:00 +0200 [thread overview]
Message-ID: <83pmmjf5x3.fsf@gnu.org> (raw)
In-Reply-To: <83r16zf6n9.fsf@gnu.org> (message from Eli Zaretskii on Fri, 18 Mar 2022 20:38:18 +0200)
> Date: Fri, 18 Mar 2022 20:38:18 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 54450@debbugs.gnu.org
>
> > Yes, this could solve the issue for the region, but not in general for
> > redisplay--update-cursor-face-highlight which was the initial problem
> > with Juri's code. Same for any other function that goes into the
> > pre-redisplay-functions hook.
>
> I asked for a test case, and this is what you gave me.
>
> If there's another test case, please show it.
But before you do, please try the alternative patch below:
diff --git a/src/xdisp.c b/src/xdisp.c
index 5cb5839..6d8d4aa 100644
--- a/src/xdisp.c
+++ b/src/xdisp.c
@@ -13211,7 +13211,8 @@ prepare_menu_bars (void)
struct window *w = XWINDOW (this);
if (w->redisplay
|| XFRAME (w->frame)->redisplay
- || XBUFFER (w->contents)->text->redisplay)
+ || XBUFFER (w->contents)->text->redisplay
+ || w->last_point != marker_position (w->pointm))
{
windows = Fcons (this, windows);
}
next prev parent reply other threads:[~2022-03-18 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pmmjw9ru.fsf.ref@aol.com>
2022-03-18 15:38 ` bug#54450: 29.0.50; redisplay--pre-redisplay-functions issue Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-18 17:01 ` Eli Zaretskii
2022-03-18 17:42 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-18 18:38 ` Eli Zaretskii
2022-03-18 18:52 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-18 19:46 ` Eli Zaretskii
2022-03-18 18:54 ` Eli Zaretskii [this message]
2022-03-18 21:25 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-19 7:22 ` Eli Zaretskii
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=83pmmjf5x3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54450@debbugs.gnu.org \
--cc=spacibba@aol.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.