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 11:10:48 +0200 [thread overview]
Message-ID: <838s9uupnr.fsf@gnu.org> (raw)
In-Reply-To: <87sg82tjf6.fsf@web.de> (message from Michael Heerdegen on Sat, 19 Dec 2020 07:10:53 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Sat, 19 Dec 2020 07:10:53 +0100
> Cc: Jonas Bernoulli <jonas@bernoul.li>
>
> (defvar my-magit-log-show-only-hash-lines-mode-keywords
> `((,(rx (and bol space (* any) eol))
> (0 (let ((beg (match-beginning 0))
> (end (1+ (match-end 0))))
> (add-text-properties beg end
> (list 'invisible 'my-magit-log-show-only-hash-lines))
> nil)))))
>
> (define-minor-mode my-magit-log-show-only-hash-lines-mode
> "..." nil nil nil
> (if (not my-magit-log-show-only-hash-lines-mode)
> (remove-from-invisibility-spec 'my-magit-log-show-only-hash-lines)
> (font-lock-add-keywords nil my-magit-log-show-only-hash-lines-mode-keywords)
> (add-to-invisibility-spec 'my-magit-log-show-only-hash-lines)))
>
> Now enable that mode in the buffer and M-x font-lock-fontify-buffer.
>
> When I now move around in the buffer with the arrow keys, it often
> happens that when point is at the beginning of a visible line, and I hit
> <right>, the echo area shows that point actually has moved backwards into
> the invisible area somewhere before that line, but the cursor is placed
> at the expected position. Further movement behaves as expected from the
> drawn cursor position, just the value of `point' sometimes is
> inconsistent, and that can cause trouble (like incorrect section
> highlighting in the Magit Log buffer).
Does setting global-disable-point-adjustment non-nil and repeating
your experiment explain what happens?
It isn't a redisplay problem.
next prev parent reply other threads:[~2020-12-19 9:10 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 [this message]
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
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=838s9uupnr.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).