From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 70386@debbugs.gnu.org
Subject: bug#70386: 30.0.50; (recenter 0 t) does not put point on top of the window
Date: Sun, 12 May 2024 06:17:49 +0000 [thread overview]
Message-ID: <87eda7tuya.fsf@localhost> (raw)
In-Reply-To: <86eda71sdx.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> (push (point) point-list)
>> (push (count-lines 1 (point)) current-line-list)
>> ;; Call original recenter for final adjustment.
>> (recenter 0 t)
>> (push (point) point-list)
>> (push (count-lines 1 (point)) current-line-list))
>>
>> point-list ; -> 757 757 757 757
>> current-line-list ; -> 21 21 21 21
>
> Try harder, that's not all the truth. In particular, what happens
> during the interpolation is not shown.
Why does it need to matter? Right before calling recenter, the point is
at 757, as you can see from point-list in my test.
Or do _previous_ point positions affect `recenter'?
> In addition, the way 'recenter' works, it is not guaranteed that point
> will end up on the line you ask it to place point. It's a "best
> effort", no more.
May you please explain how I am supposed to know this from reading the
docstring?
With a numeric prefix argument ARG, recenter putting point on screen line ARG
relative to the selected window. If ARG is negative, it counts up from the
bottom of the window. (ARG should be less than the height of the window.)
>> Maybe. But I do believe that my reproducer demonstrates a bug.
>
> Why do you still believe that? What will it take to convince you that
> in the situation your recipe creates the result can sometimes be not
> what you want?
At least, a docstring that explains what `recenter' does better.
And even then, when scrolling current line to be on the top (which is
what (recenter 0 t) supposed to do), as a user, I will be surprised that
the current line remains at line 21! - what kind of "best effort" is
that when the result if off by 21 lines? surely, Emacs can do better.
--
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:[~2024-05-12 6:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 16:33 bug#70386: 30.0.50; (recenter 0 t) does not put point on top of the window Ihor Radchenko
2024-04-14 19:00 ` Eli Zaretskii
2024-04-14 19:36 ` Ihor Radchenko
2024-04-15 16:11 ` Eli Zaretskii
2024-04-15 17:13 ` Ihor Radchenko
2024-04-15 18:29 ` Eli Zaretskii
[not found] ` <87cyqq5usj.fsf@localhost>
2024-04-15 19:14 ` Eli Zaretskii
2024-04-27 8:29 ` Eli Zaretskii
2024-04-27 10:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-27 11:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-29 18:31 ` Ihor Radchenko
2024-05-09 7:37 ` Eli Zaretskii
2024-05-09 7:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 17:48 ` Ihor Radchenko
2024-05-11 17:56 ` Eli Zaretskii
2024-05-11 18:00 ` Ihor Radchenko
2024-05-11 18:26 ` Eli Zaretskii
2024-05-11 18:42 ` Ihor Radchenko
2024-05-11 18:53 ` Eli Zaretskii
2024-05-11 19:09 ` Ihor Radchenko
2024-05-12 6:00 ` Eli Zaretskii
2024-05-12 6:17 ` Ihor Radchenko [this message]
2024-05-12 6:39 ` Eli Zaretskii
2024-05-12 6:58 ` Ihor Radchenko
2024-05-12 7:02 ` Eli Zaretskii
2024-05-12 7:17 ` Ihor Radchenko
2024-05-12 9:17 ` Eli Zaretskii
2024-05-12 9:23 ` Ihor Radchenko
2024-05-12 10:15 ` Eli Zaretskii
2024-05-12 7:19 ` Ihor Radchenko
2024-05-12 9:19 ` Eli Zaretskii
2024-05-19 13:49 ` Ihor Radchenko
2024-05-19 15:29 ` Eli Zaretskii
2024-05-23 13:27 ` Eli Zaretskii
2024-05-23 13:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87eda7tuya.fsf@localhost \
--to=yantar92@posteo.net \
--cc=70386@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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.