all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mats Lidell <matsl@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Odd behavior when moving point over invisible text
Date: Tue, 06 Jun 2023 15:22:58 +0300	[thread overview]
Message-ID: <83legw3hlp.fsf@gnu.org> (raw)
In-Reply-To: <87zg5cpzf8.fsf@gnu.org> (message from Mats Lidell on Tue, 06 Jun 2023 14:07:07 +0200)

> From: Mats Lidell <matsl@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Tue, 06 Jun 2023 14:07:07 +0200
> 
>    Put the point one char away from the ellipsis. Press C-f twice and point
>    moves up to the ellipsis and over it. If I instead do C-u 2 C-f the point
>    will stop at the ellipsis.
> 
> > What exactly are your expectations from this heuristic?
> 
> I would expect both ways to move the point to produce the same result.

Why?  In the first case, Emacs knows you stopped between the two
moves, in the second one you didn't.

> For my initial quest to write some unit tests around hidden text I feel better
> equipped now. I understand why (forward-char) twice can't be used in the unit
> test to move past the ellipsis since that behavior is connected to the
> heuristics that will not kick in.

If you are writing tests, you are better off disabling point
adjustments altogether.  See global-disable-point-adjustment.



  reply	other threads:[~2023-06-06 12:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 21:43 Odd behavior when moving point over invisible text Mats Lidell
2023-06-05  7:09 ` Karl Fogel
2023-06-05 13:05   ` Eli Zaretskii
2023-06-05 17:51     ` Karl Fogel
2023-06-05 19:38     ` Mats Lidell
2023-06-05 12:59 ` Eli Zaretskii
2023-06-05 23:30   ` Mats Lidell
2023-06-06 11:48     ` Eli Zaretskii
2023-06-06 12:07       ` Mats Lidell
2023-06-06 12:22         ` Eli Zaretskii [this message]
2023-06-06 22:45           ` Mats Lidell

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=83legw3hlp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=matsl@gnu.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 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.