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

Keyboard scroll (Scroll Lock plus ↑, ↓, PgUp, PgDn) #9148

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

Originally created by @martingbrown on GitHub (Jun 19, 2020).

Currently when I press the up and down arrows, terminal (or it may be PowerShell/Cmd) switches between my most recently used commands. I'd also like to be able to scroll the screen, similarly to how the scroll bar works, using the keyboard.

My proposal would be to use the Scroll Lock key to toggle between two modes. With scroll lock off it would work as it does now, with scroll lock on the Up and Down arrows would scroll a single line (or repeatedly scroll one line if held down) and the Page Up, Page Down keys would scroll an entire window full.

Excel has similar functionality. With scroll lock off the selected cell moves, with scroll lock on it doesn't.

Originally created by @martingbrown on GitHub (Jun 19, 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! --> <!-- 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). --> Currently when I press the up and down arrows, terminal (or it may be PowerShell/Cmd) switches between my most recently used commands. I'd also like to be able to scroll the screen, similarly to how the scroll bar works, using the keyboard. <!-- A clear and concise description of what you want to happen. --> My proposal would be to use the Scroll Lock key to toggle between two modes. With scroll lock off it would work as it does now, with scroll lock on the Up and Down arrows would scroll a single line (or repeatedly scroll one line if held down) and the Page Up, Page Down keys would scroll an entire window full. Excel has similar functionality. With scroll lock off the selected cell moves, with scroll lock on it doesn't.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:47:12 +00:00
claunia commented 2026-01-31 01:47:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 19, 2020):

There's already the following keybindings if you want to use the keyboard to navigate the scrollback:
1fdceb0ea9/src/cascadia/TerminalApp/defaults.json (L331-L334)

Do those work for you?

@zadjii-msft commented on GitHub (Jun 19, 2020): There's already the following keybindings if you want to use the keyboard to navigate the scrollback: https://github.com/microsoft/terminal/blob/1fdceb0ea99f968142cb014286baa362c65d6b3f/src/cascadia/TerminalApp/defaults.json#L331-L334 Do those work for you?
claunia commented 2026-01-31 01:47:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 23, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 23, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 01:47:14 +00:00
Author
Owner
Copy Link

@martingbrown commented on GitHub (Jun 24, 2020):

I guess that does work, but I still think it would make the finger gymnastics a bit easier to use scroll lock.

@martingbrown commented on GitHub (Jun 24, 2020): I guess that does work, but I still think it would make the finger gymnastics a bit easier to use scroll lock.
claunia commented 2026-01-31 01:47:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 26, 2020):

I agree. We've got a couple specs in flight here (#2529, for #980), and #3863 mentions scroll lock. Once we have keyboard selection (#2840 spec), that'll include keyboard buffer navigation, and we can extend #2529 to cover scroll lock as well. We're also considering "mark" mode (a mode you switch into where you can navigate the buffer solely by keyboard)

/dup #3863, #715

@DHowett commented on GitHub (Jun 26, 2020): I agree. We've got a couple specs in flight here (#2529, for #980), and #3863 mentions scroll lock. Once we have keyboard selection (#2840 spec), that'll include keyboard buffer navigation, and we can extend #2529 to cover scroll lock as well. We're also considering "mark" mode (a mode you switch into where you can navigate the buffer solely by keyboard) /dup #3863, #715
claunia commented 2026-01-31 01:47:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 26, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 26, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 01:47:15 +00:00
Author
Owner
Copy Link

@martingbrown commented on GitHub (Jun 26, 2020):

Thanks Dustin, sounds like you've got this covered.

@martingbrown commented on GitHub (Jun 26, 2020): Thanks Dustin, sounds like you've got this covered.
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 Issue-Feature Resolution-Duplicate
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#9148
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?