From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: jonas@bernoul.li, 45319@debbugs.gnu.org
Subject: bug#45319: 28.0.50; Redisplay: `forward-char' moves backwards into invisible text
Date: Sat, 19 Dec 2020 15:05:25 +0200 [thread overview]
Message-ID: <83r1nmt08a.fsf@gnu.org> (raw)
In-Reply-To: <877dpem0dm.fsf@web.de> (message from Michael Heerdegen on Sat, 19 Dec 2020 13:44:05 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 45319@debbugs.gnu.org, jonas@bernoul.li
> Date: Sat, 19 Dec 2020 13:44:05 +0100
>
> Magit's section highlighting is performed in post-command-hook, so it
> highlights the wrong section in this case based on that value. Do you
> have a solution for this kind of problem?
I don't think I understand the problem well enough yet to answer that
question, especially since you say that your simplified recipe behaves
differently.
What exactly is the problem in the magit case? does it use the value
of point in some way, and if so, how? IOW, what is "section
highlighting" in magit?
> Ok, have tried now with (setq global-disable-point-adjustment t) and it
> avoids the problem in my test case, yes. However it's not what I want
> to do in this buffer (or generally in this kind of situation, most of
> the time).
A stab in the dark: there's disable-point-adjustment, which could be
set temporarily, perhaps that could help?
next prev parent reply other threads:[~2020-12-19 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 6:10 bug#45319: 28.0.50; Redisplay: `forward-char' moves backwards into invisible text Michael Heerdegen
2020-12-19 9:10 ` Eli Zaretskii
2020-12-19 11:21 ` Michael Heerdegen
2020-12-19 11:26 ` Eli Zaretskii
2020-12-19 12:09 ` Michael Heerdegen
2020-12-19 12:19 ` Eli Zaretskii
2020-12-19 12:44 ` Michael Heerdegen
2020-12-19 13:05 ` Eli Zaretskii [this message]
2020-12-20 2:15 ` Michael Heerdegen
2020-12-20 3:32 ` Michael Heerdegen
2020-12-20 8:01 ` Michael Heerdegen
2020-12-20 15:38 ` 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
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=83r1nmt08a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45319@debbugs.gnu.org \
--cc=jonas@bernoul.li \
--cc=michael_heerdegen@web.de \
/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).