-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Specify number of lines for scollUp and scrollDown commands (+ follow system setting?) #5078
Comments
We've got a global setting, |
I was talking about the keyboard-bindable commands :) |
You know, when I first spec'd arguments for keybindings, I called out |
@zadjii-msft For me personally it would actually be enough if the value was simply linked to (accidentally hit the close issue button there) |
Thanks! Triaged this onto the backlog, but marked it Help-Wanted. If somebody were to implement this before v1, I'd almost certainly pull it in. |
- The number of lines to move upon scroll up scroll down can be defined in ScrollUp and ScrollDown commands (parameter is called "rowsToScroll"). - If the number are not provided, use the system default (the one we are using for mouse scrolls), rather than 1 line. ## Validation Steps Performed * Manual testing * Added custom bindings for scroll commands with different values, verified they and the default appear and behave as expected * Checked that invalid values are not allowed Closes #5078
🎉This issue was addressed in #7924, which has now been successfully released as Handy links: |
Description of the new feature/enhancement
It would be nice if the
scrollUp
andscrollDown
commands supported alines
argument that would specify how many lines to scroll.Alternatively or additionally, it might make sense to set the default to the number of lines the mouse wheel is set to scroll, i.e. usually 3. This seems more useful to me as a default than just scrolling a single line, which is very slow, or scrolling a whole page, which can be jarring (at least without smooth scrolling #1400).
Proposed technical implementation details (optional)
The text was updated successfully, but these errors were encountered: