From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 66769@debbugs.gnu.org, aaronjensen@gmail.com
Subject: bug#66769: 30.0.50; pixel-scroll-precision-mode and scroll-margin regression
Date: Sat, 28 Oct 2023 11:29:07 +0300 [thread overview]
Message-ID: <83sf5vcfqk.fsf@gnu.org> (raw)
In-Reply-To: <87ttqbw66m.fsf@yahoo.com> (message from Po Lu on Sat, 28 Oct 2023 15:35:13 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: aaronjensen@gmail.com, 66769@debbugs.gnu.org
> Date: Sat, 28 Oct 2023 15:35:13 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What is the "target point" in the above text? target for what?
>
> The position where point will be moved after the window start and
> vscroll are adjusted, which is such that redisplay will not recenter or
> otherwise undermine the scrolling operation.
And what are the problems in computing this target point in the
particular case described here?
> > Why not use the too-slow posn-at-point, but only in this case?
>
> Because with that, precision scrolling slows down to a crawl.
Even if it's done "only in this case"? It should slow down only this
case, no?
And what exactly is the crucial difference between "this case" and the
other cases, where scrolling works correctly?
next prev parent reply other threads:[~2023-10-28 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 5:00 bug#66769: 30.0.50; pixel-scroll-precision-mode and scroll-margin regression Aaron Jensen
2023-10-28 2:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 6:43 ` Eli Zaretskii
2023-10-28 7:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 8:29 ` Eli Zaretskii [this message]
2023-10-28 8:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 8:42 ` Eli Zaretskii
2023-10-28 12:33 ` Aaron Jensen
2023-10-28 12:54 ` Eli Zaretskii
2023-11-02 5:49 ` Aaron Jensen
2023-11-02 6:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-02 6:28 ` Eli Zaretskii
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=83sf5vcfqk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66769@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--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 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).