From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Thu, 20 Jul 2023 09:57:02 +0000 [thread overview]
Message-ID: <875y6erjm9.fsf@localhost> (raw)
In-Reply-To: <jwvo7k7retq.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Indeed, the `set_point_both` adjustment is an obsolete (mis-)feature
> that has been deprecated since Emacs-25, when
> `inhibit-point-motion-hooks`s default has been changed to t (and
> replaced with `cursor-sensor-mode` and
> `cursor-intangible-mode`).
Will it ever be removed though?
It appears to affect outline mode a lot.
We just recently received a somewhat related report with yet another
point adjustment subtlety:
* Short heading...
* Very very very very long heading<point>...
C-p will move after hidden text above:
* Short heading...<point>
* Very very very very long heading...
And I am pretty sure that there are many edge cases like this, which
rely on the implementation details with point adjustment.
--
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-20 9:57 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 [this message]
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
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=875y6erjm9.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).