From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 64724@debbugs.gnu.org
Subject: bug#64724: 30.0.50; Inconsistency between manual, comments in the code, and implementation of point adjustment
Date: Fri, 21 Jul 2023 10:58:11 -0400 [thread overview]
Message-ID: <jwvpm4lnwgj.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87tttx7leo.fsf@localhost> (Ihor Radchenko's message of "Fri, 21 Jul 2023 07:50:55 +0000")
Ihor Radchenko [2023-07-21 07:50:55] wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> So, there is no problem with this section of the manual. The problem is
>>> that manual does not describe the behavior with invisible text
>>> boundaries I was trying to figure out.
>>
>> Which aspects of the behavior you describe are not mentioned in the
>> manual. It does refer to invisible text.
>
> It talks about "in the middle of a sequence .. that ... is invisible"
>
> Emacs cannot display the cursor when point is in the middle of a
> sequence of text that has the ‘display’ or ‘composition’ property, or is
> invisible. Therefore, after a command finishes and returns to the
> command loop, if point is within such a sequence, the command loop
> normally moves point to the edge of the sequence, making this sequence
> effectively intangible.
>
> The situation I encountered is when point ends up not in the middle, but
> already on the edge. So, Emacs moving point to _other_ edge was
> surprising.
How 'bout the rephrasing below?
Stefan
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 037f42124cc..ca009d97b39 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -1253,12 +1253,13 @@ Adjusting Point
@cindex @code{display} property, and point display
@cindex @code{composition} property, and point display
- Emacs cannot display the cursor when point is in the middle of a
-sequence of text that has the @code{display} or @code{composition}
-property, or is invisible. Therefore, after a command finishes and
-returns to the command loop, if point is within such a sequence, the
-command loop normally moves point to the edge of the sequence, making this
-sequence effectively intangible.
+ When point is in the middle of a sequence of text that has the
+@code{display} or @code{composition} property, or is invisible, Emacs
+there can be several buffer positions that result in the cursor being
+displayed at same place. Therefore, after a command finishes and
+returns to the command loop, if point is in such a sequence, the
+command loop normally moves point to one of the two edges of the
+sequence, making this sequence effectively intangible.
A command can inhibit this feature by setting the variable
@code{disable-point-adjustment}:
next prev parent reply other threads:[~2023-07-21 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 7:02 bug#64724: 30.0.50; Inconsistency between manual, comments in the code, and implementation of point adjustment Ihor Radchenko
2023-07-19 16:43 ` Eli Zaretskii
2023-07-19 17:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20 9:57 ` Ihor Radchenko
2023-07-21 2:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20 9:51 ` Ihor Radchenko
2023-07-20 10:27 ` Eli Zaretskii
2023-07-21 7:50 ` Ihor Radchenko
2023-07-21 10:51 ` Eli Zaretskii
2023-07-21 12:14 ` Ihor Radchenko
2023-07-21 12:44 ` Eli Zaretskii
2023-07-21 12:56 ` Ihor Radchenko
2023-07-21 13:07 ` Eli Zaretskii
2023-07-21 13:18 ` Ihor Radchenko
2023-07-21 14:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-21 15:15 ` Eli Zaretskii
2023-07-22 13:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-23 6:54 ` Ihor Radchenko
2023-07-22 6:13 ` Ihor Radchenko
2023-07-21 2:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-21 9:11 ` Ihor Radchenko
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=jwvpm4lnwgj.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=64724@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@posteo.net \
/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).