-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement alternateScroll settings #5194
Comments
Note that it might be relevant if high-resolution scrolling is supported or not. I'm only seeing this in a VNC environment that only has the classical "stepped" wheel events. |
Thats related to this line: xterm.js/src/browser/CoreBrowserTerminal.ts Line 813 in f701d07
As far as I can see with git blame, it has always been like that in the last 6 years.
Which terminals show that behavior? (xterm does not on my system...) |
That might very well be. I'm a new vscode user, so I'm comparing to other terminals, not to any previous xterm.js behaviour. :)
Odd. I'm seeing it in xterm¹, GNOME terminal and MATE terminal (fork of GNOME 2 terminal). Tested on RHEL 9 and Fedora 40. Three lines is also what xterm.js scrolls per click for me in the "normal" scrollback, so it's a bit confusing when the scroll distance changes when I open a ¹ xterm actually jumps 5 lines for me, not 3 |
Perhaps that sequence should be multiplied by the various settings affecting the scrollback, so they stay in sync? |
I checked the xterm sources - thats basically linked there to
I agree, we should strive to sync that with other scroll handling like on the normal scroll buffer. So what we need here:
|
Details
Steps to reproduce
less file.txt
Expected outcome
File scrolls the same 3 lines you get in the scrollback buffer, or as commonly seen in almost all other terminals.
Actual outcome
File scrolls a single line.
Additional details
If I do an strace of
less
, I can see the other terminals send three\33OB
on one mouse scroll click, whilst xterm.js only sends the one. Which fully explains things.I couldn't find any setting in vscode that affected this. Workarounds are welcome.
The text was updated successfully, but these errors were encountered: