GNU bug report logs - #66769
30.0.50; pixel-scroll-precision-mode and scroll-margin regression

Previous Next

Full log

Message #17 received at 66769 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 66769 <at> debbugs.gnu.org, aaronjensen <at> gmail.com
Subject: Re: bug#66769: 30.0.50; pixel-scroll-precision-mode and
 scroll-margin regression
Date: Sat, 28 Oct 2023 11:29:07 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: aaronjensen <at> gmail.com,  66769 <at> debbugs.gnu.org
> Date: Sat, 28 Oct 2023 15:35:13 +0800
> 
> Eli Zaretskii <eliz <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.