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 13:26:01 +0200 [thread overview]
Message-ID: <83v9cyt4ty.fsf@gnu.org> (raw)
In-Reply-To: <87ft42m47c.fsf@web.de> (message from Michael Heerdegen on Sat, 19 Dec 2020 12:21:27 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 45319@debbugs.gnu.org, jonas@bernoul.li
> Date: Sat, 19 Dec 2020 12:21:27 +0100
>
> > Does setting global-disable-point-adjustment non-nil and repeating
> > your experiment explain what happens?
>
> I currently can't try because I'm eating ATM (yeah, shouldn't read mails
> while eating...) but in the Magit buffer that was the first thing I had
> tried and it didn't have an effect.
then maybe your recipe is not a complete demonstration what happens in
Magit buffers.
> > It isn't a redisplay problem.
>
> Point is moved from a visible into an invisible area - that should not
> happen, no? Even with point-adjustment enabled.
Why not? "Invisible" means it is not displayed, but it doesn't mean
point cannot be there. We have point-adjustment to avoid confusing
users because otherwise when point enters invisible text, cursor
movement commands would seem to have no effect, but that doesn't mean
point cannot enter invisible text.
next prev parent reply other threads:[~2020-12-19 11:26 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9cyt4ty.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 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.