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

Previous Next

Full log

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

From: Steven Allen <steven <at> stebalien.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: luangruo <at> yahoo.com, 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 11:40:42 -0700

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Steven Allen <steven <at> stebalien.com>
>> Cc: luangruo <at> yahoo.com, 72323 <at> debbugs.gnu.org, storm <at> cua.dk
>> Date: Sun, 18 Aug 2024 10:38:29 -0700
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> > Once again: the vscroll value is pertinent only for the screen line
>> > for which it was computed, because the way it is computed uses the
>> > metrics of that line.  Once you move to another line, the value is no
>> > longer pertinent.
>> 
>> Let's be precise about "move to another line":
>> 
>> - When window-start changes, vscroll becomes invalid because the lines at
>>   the top of the screen (to which vscroll applies) has changed. I agree
>>   that it must be reset in this case.
>> - When point is moved up and down in such a way that window-start isn't
>>   changed, vscroll is still perfectly valid as the top line in the
>>   window hasn't changed.
>
> I disagree.  When point moves to another screen line without moving
> window-start, vscroll may or may not be valid.  Whether it is depends
> on the details of what is on display.

Can you give me an example example where moving point invalidates
vscroll (except when point would move partially or fully off screen)?

Previous Next

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