From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: dmitry.kurochkin@gmail.com, 9034@debbugs.gnu.org
Subject: bug#9034: point adjustment (with invisible text) moves to the next line
Date: Thu, 26 Aug 2021 18:46:37 +0300 [thread overview]
Message-ID: <8335qwtdia.fsf@gnu.org> (raw)
In-Reply-To: <877dg82u6n.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 26 Aug 2021 15:48:32 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: dmitry.kurochkin@gmail.com, 9034@debbugs.gnu.org
> Date: Thu, 26 Aug 2021 15:48:32 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This code is chock-full of questionable heuristics, and in particular
> > tries to guess in which direction to move point out of the invisible
> > text. The results are sometimes surprising. The upside is that it
> > "mostly works". But if someone can come up with a better heuristics,
> > I'm all ears.
>
> Ah, right. But... the super-confusing thing about this is that we're
> not moving point in the buffer at all.
The original recipe moved from point-min to an end of a line.
> Just doing `M-: 4 RET' will result in this code adjusting point in
> the buffer. Doing, for instance, `M-x foo RET' (where `foo' does
> nothing) does not result in this point movement.
>
> So is `M-:' doing some weird thing in the original buffer to trigger
> this oddity?
Doing M-: in what part of the recipe?
next prev parent reply other threads:[~2021-08-26 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 13:04 bug#9034: point adjustment after `end-of-visual-line' moves to the next line Dmitry Kurochkin
2011-07-11 4:16 ` Stefan Monnier
2011-07-11 8:27 ` Dmitry Kurochkin
2021-08-25 16:32 ` bug#9034: point adjustment (with invisible text) " Lars Ingebrigtsen
2021-08-25 16:43 ` Eli Zaretskii
2021-08-26 13:48 ` Lars Ingebrigtsen
2021-08-26 15:46 ` Eli Zaretskii [this message]
2021-08-26 16:33 ` Lars Ingebrigtsen
2021-08-26 16:48 ` Eli Zaretskii
2021-08-26 17:05 ` Lars Ingebrigtsen
2021-08-26 17:13 ` 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=8335qwtdia.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9034@debbugs.gnu.org \
--cc=dmitry.kurochkin@gmail.com \
--cc=larsi@gnus.org \
/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).