unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: jonas@bernoul.li, 45319-done@debbugs.gnu.org
Subject: bug#45319: 28.0.50; Redisplay: `forward-char' moves backwards into invisible text
Date: Sun, 20 Dec 2020 17:38:26 +0200	[thread overview]
Message-ID: <83wnxcsd1p.fsf@gnu.org> (raw)
In-Reply-To: <87h7ogykgf.fsf@web.de> (message from Michael Heerdegen on Sun, 20 Dec 2020 09:01:52 +0100)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 45319@debbugs.gnu.org,  jonas@bernoul.li
> Date: Sun, 20 Dec 2020 09:01:52 +0100
> 
> I see now that that problem has been discussed in Bug#23079.  If you
> think that everything is alright with my test case you might close this
> bug and probably merge with that one.

I closed this one.  Merging them is too much of a hassle with
debbugs's unhelpful defaults for archived bugs.

The only other thing I could say, which may or may not be helpful for
your use case, is that Lisp programs shouldn't assume they will always
find point outside of invisible portion of the text, and instead
actively look for the first visible position after point.





      reply	other threads:[~2020-12-20 15:38 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
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 [this message]

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=83wnxcsd1p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45319-done@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).