From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64724@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#64724: 30.0.50; Inconsistency between manual, comments in the code, and implementation of point adjustment
Date: Fri, 21 Jul 2023 12:14:55 +0000 [thread overview]
Message-ID: <87iladmpfk.fsf@localhost> (raw)
In-Reply-To: <83cz0l1qsn.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
>
> That's because where to move point in these situations depends on
> where it was before. We could describe these details of the
> heuristics we use, but I very much doubt it will be useful in
> practice. And the heuristics could change in the future, which makes
> this a maintenance problem.
I think you misunderstood.
I know that the logic how Emacs chooses which boundary to move to is not
documented.
However, my problem is not with this logic. My problem is that info page
says that point adjustment happens when point is _inside_ invisible
region. However, in my situation the point is already at the boundary
(that is: _not inside_).
> So I tend to think this bug should be closed with no further action.
> The main purpose of that node is to explain how to disable this point
> adjustment, not describe in detail what it does and how.
Please remember that info page was just one of the points I listed in
the initial report.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-07-21 12:14 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 [this message]
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
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=87iladmpfk.fsf@localhost \
--to=yantar92@posteo.net \
--cc=64724@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).