From: Steven Allen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 72323@debbugs.gnu.org, storm@cua.dk
Subject: bug#72323: 31.0.50; line-move unconditionally resets vscroll to 0
Date: Sun, 18 Aug 2024 10:38:29 -0700 [thread overview]
Message-ID: <877ccd3f56.fsf@stebalien.com> (raw)
In-Reply-To: <86jzh4zc2w.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Steven Allen <steven@stebalien.com>
>> Cc: 72323@debbugs.gnu.org, storm@cua.dk
>> Date: Sun, 28 Jul 2024 13:07:09 -0700
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > vscroll is not just about scrolling the window. It is basically a
>> > vertical offset from the screen line that shows window-start to the
>> > top-most pixel shown in the window. It is meant to enable to see the
>> > tall screen line at window-start in its entirety. Once point moves
>> > off that screen line, vscroll is no longer pertinent, since the
>> > important line, for which vscroll has been determined, has changed.
>> > For example, imagine that the line into which point moves cannot be
>> > displayed in its entirety with this vscroll, because it starts at a
>> > different vertical coordinate (so its lower part could be below the
>> > window bottom).
>>
>> No? E.g., if I have half a line (or half an image) visible and move my
>> point off that line, I wouldn't expect that line to suddenly scroll out
>> of view _unless_ the entire screen needs to scroll because the
>> text/image is larger than the entire screen.
>
> It depends on the details of the line from which you move cursor and
> the one into which you move. For example, if the former takes up
> almost the entire window, then moving into the next one could cause
> that next line to be only partially visible, and that is unacceptable
> for the Emacs redisplay.
In that case I completely agree. If point moves to a partially displayed
line, vscroll needs to be adjusted and/or reset.
> 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. vscroll is relative to the top line, not point.
> Emacs supports smooth scrolling only within a single screen line, and
> that uses vscroll. That's the original design intent of vscroll.
> Smooth scrolling between lines is not really supported.
> pixel-scrolling attempts to solve that, and does it well, but it does
> have some problematic corners. Those corners need to be solved inside
> pixel-scroll code.
Honestly, scrolling between lines is working perfectly. I'm not running
into issues when scrolling, I'm running into issues when changing lines
after partially scrolling a line.
next prev parent reply other threads:[~2024-08-18 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 17:57 bug#72323: 31.0.50; line-move unconditionally resets vscroll to 0 Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27 18:11 ` Eli Zaretskii
2024-07-27 20:10 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 4:50 ` Eli Zaretskii
2024-07-28 20:07 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 20:10 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-29 11:14 ` Eli Zaretskii
2024-07-29 11:12 ` Eli Zaretskii
2024-07-29 14:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-18 17:42 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-18 17:38 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-08-18 18:21 ` Eli Zaretskii
2024-08-18 18:40 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-18 19:01 ` Eli Zaretskii
2024-08-18 22:17 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-19 11:06 ` Eli Zaretskii
2024-08-19 17:30 ` Steven Allen 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
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=877ccd3f56.fsf@stebalien.com \
--to=bug-gnu-emacs@gnu.org \
--cc=72323@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=steven@stebalien.com \
--cc=storm@cua.dk \
/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).