starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Specify number of lines for scollUp and scrollDown commands (+ follow system setting?) #7093

New Issue
Closed
opened 2026-01-31 00:54:45 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:54:45 +00:00
Owner
Copy Link

Originally created by @Livven on GitHub (Mar 22, 2020).

Description of the new feature/enhancement

It would be nice if the scrollUp and scrollDown commands supported a lines 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)

Originally created by @Livven on GitHub (Mar 22, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> It would be nice if the `scrollUp` and `scrollDown` commands supported a `lines` 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) <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-31 00:54:47 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 22, 2020):

We've got a global setting, "rowsToScroll", that configures how many lines to scroll with the wheel. If you do not set it, it defaults to your system setting (as set in the Mouse settings page.) If I recall, that default on Windows is 3.
If you're using a precision trackpad, that setting should still apply.

@DHowett-MSFT commented on GitHub (Mar 22, 2020): We've got a global setting, `"rowsToScroll"`, that configures how many lines to scroll with the wheel. If you do not set it, it defaults to your system setting (as set in the Mouse settings page.) If I recall, that default on Windows is 3. If you're using a precision trackpad, that setting should still apply.
claunia commented 2026-01-31 00:54:47 +00:00
Author
Owner
Copy Link

@Livven commented on GitHub (Mar 22, 2020):

I was talking about the keyboard-bindable commands :)

@Livven commented on GitHub (Mar 22, 2020): I was talking about the keyboard-bindable commands :)
claunia commented 2026-01-31 00:54:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 23, 2020):

You know, when I first spec'd arguments for keybindings, I called out scrollUp and scrollDown as two actions that needed args for customizable values. Looks like that never got turned into an actual issue.

@zadjii-msft commented on GitHub (Mar 23, 2020): You know, when I first [spec'd arguments for keybindings](https://github.com/microsoft/terminal/blob/master/doc/specs/%231142%20-%20Keybinding%20Arguments.md), I called out `scrollUp` and `scrollDown` as two actions that needed args for customizable values. Looks like that never got turned into an actual issue.
claunia commented 2026-01-31 00:54:47 +00:00
Author
Owner
Copy Link

@Livven commented on GitHub (Mar 23, 2020):

@zadjii-msft For me personally it would actually be enough if the value was simply linked to rowsToScroll or the Windows mouse wheel setting, because that already fixes the issue of scrolling by just 1 line being super slow. But of course additional customization doesn't hurt.

(accidentally hit the close issue button there)

@Livven commented on GitHub (Mar 23, 2020): @zadjii-msft For me personally it would actually be enough if the value was simply linked to `rowsToScroll` or the Windows mouse wheel setting, because that already fixes the issue of scrolling by just 1 line being super slow. But of course additional customization doesn't hurt. (accidentally hit the close issue button there)
claunia commented 2026-01-31 00:54:48 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 24, 2020):

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.

@DHowett-MSFT commented on GitHub (Mar 24, 2020): 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.
claunia commented 2026-01-31 00:54:48 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 11, 2020):

:tada:This issue was addressed in #7924, which has now been successfully released as Windows Terminal Preview v1.5.3142.0.🎉

Handy links:

@ghost commented on GitHub (Nov 11, 2020): :tada:This issue was addressed in #7924, which has now been successfully released as `Windows Terminal Preview v1.5.3142.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.5.3142.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Settings Help Wanted Issue-Task Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7093
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?