unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
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:09:49 +0100	[thread overview]
Message-ID: <87bleqm1yq.fsf@web.de> (raw)
In-Reply-To: <83v9cyt4ty.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Dec 2020 13:26:01 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> 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.

But in the situation I described, I have been starting at a visible
position, `forward-char' should move point to the next char which is
also a visible, instead Emacs moves point some characters backwards into
an unrelated invisible position, that makes no sense to me.

Michael.





  reply	other threads:[~2020-12-19 12:09 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 [this message]
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=87bleqm1yq.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=45319@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jonas@bernoul.li \
    /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).