GNU bug report logs - #72323
31.0.50; line-move unconditionally resets vscroll to 0

Previous Next

Full log

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

From: Steven Allen <steven <at> stebalien.com>
To: Po Lu <luangruo <at> yahoo.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 72323 <at> debbugs.gnu.org, storm <at> cua.dk
Subject: Re: bug#72323: 31.0.50; line-move unconditionally resets vscroll to 0
Date: Sun, 18 Aug 2024 10:42:25 -0700

Po Lu <luangruo <at> yahoo.com> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> This function is very clearly about cursor motion, not scrolling, and
>>> shouldn't mess with the current scroll position.
>>
>> Po Lu will tell, but my understanding of the comment is that it does
>> what it does out of necessity.
>
> I don't understand why it is inherently improper that line motion
> commands should reset vscroll, which is never set to a large value by
> precision scrolling.

E.g., let's say I'm viewing an org-mode file with embedded images. With
pixel-scroll-precision-mode, I can scroll through this file, letting the
images scroll off-screen by using the vscroll offset instead of having
them suddenly "jump" off screen as I scroll by them.

However, once I start typing, the second I try to change lines the
entire screen jumps because the entire image is now forced on-screen (if
it fits) or offscreen (if it doesn't). This is extremely jarring.

Previous Next

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