Add configurable mouse wheel scroll lines (fixes #871) #872
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add WheelScrollLines config option to control mouse wheel scroll speed - Update WheelScrollNum from config.WheelScrollLines if specified - Add documentation and examples in ov.yaml and ov-less.yaml - Maintain backward compatibility with default value of 2 lines This allows users to customize mouse wheel scroll speed to match their terminal settings, addressing the inconsistency mentioned in issue #871.
- Rename WheelScrollLines config option to VScrollLines for clarity - Move VScrollLines from top-level config to General section - Update config examples in ov.yaml and ov-less.yaml to show VScrollLines alongside HScrollWidth
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows users to customize mouse wheel scroll speed to match their terminal settings, addressing the inconsistency mentioned in issue #871.