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

Idea: Align Terminal keymappings with VS Code conventions #4375

New Issue
Closed
opened 2026-01-30 23:45:26 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:45:26 +00:00
Owner
Copy Link

Originally created by @aaronsteers on GitHub (Oct 9, 2019).

Originally assigned to: @cinnamon-msft on GitHub.

Description of the new feature/enhancement

Would be great if we could align Terminal keybinding settings with the VS Code keybinding conventions (link below).

Currently, the shortcut keys abbreviations do not match and this makes it more difficult to get started with keybindings - requiring users to try to do tons of digging to find the right convention - for example, to know page down is 'pgdn' (Terminal) instead of 'pagedown' (VS Code).

Would be fantastic if we could memorize and use a single convention rather than inventing a new one and trying to remember which convention works in which tool.

Proposed technical implementation details (optional)

The Terminal shortcut key abbreviations are documented here:
(Couldn't find any reference docs. Eventually found examples by holding Ctr while selecting "Settings" in order to get to the defaults.json file.)

The VS Code shortcut key abbreviations are documented here:
https://code.visualstudio.com/docs/getstarted/keybindings#_accepted-keys

For example of the problem currently, "Page Up" is "pgup" in Terminal profiles.json and "pageup" in VS Code.

Originally created by @aaronsteers on GitHub (Oct 9, 2019). Originally assigned to: @cinnamon-msft on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Would be great if we could align Terminal keybinding settings with the VS Code keybinding conventions (link below). Currently, the shortcut keys abbreviations do not match and this makes it more difficult to get started with keybindings - requiring users to try to do tons of digging to find the right convention - for example, to know page down is 'pgdn' (Terminal) instead of 'pagedown' (VS Code). Would be fantastic if we could memorize and use a single convention rather than inventing a new one and trying to remember which convention works in which tool. <!-- 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). --> # Proposed technical implementation details (optional) The Terminal shortcut key abbreviations are documented here: `(Couldn't find any reference docs. Eventually found examples by holding Ctr while selecting "Settings" in order to get to the defaults.json file.)` The VS Code shortcut key abbreviations are documented here: https://code.visualstudio.com/docs/getstarted/keybindings#_accepted-keys For example of the problem currently, "Page Up" is "pgup" in Terminal `profiles.json` and "pageup" in VS Code. <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-30 23:45:27 +00:00
Author
Owner
Copy Link

@Pertel commented on GitHub (Oct 16, 2019):

Hey, I was having the exact same problem when trying to configure keybindings using page-up and page-down; I couldn't find any documentation with all the valid keys and had to dig around in the source code.

If you'd like, I could update the documentation to list all possible keys and submit a PR.

My suggestion is to grab the keys from KeyChordSerialization.cpp
And include them in the Profiles.json Documentation file under the keybindings section.

Even if that doesn't create parity with VS Code keybindings, it would be helpful for users creating keybindings.

@Pertel commented on GitHub (Oct 16, 2019): Hey, I was having the exact same problem when trying to configure keybindings using page-up and page-down; I couldn't find any documentation with all the valid keys and had to dig around in the source code. If you'd like, I could update the documentation to list all possible keys and submit a PR. My suggestion is to grab the keys from [KeyChordSerialization.cpp](https://github.com/microsoft/terminal/blob/master/src/cascadia/TerminalApp/KeyChordSerialization.cpp) And include them in the [Profiles.json Documentation](https://github.com/microsoft/terminal/blob/master/doc/cascadia/SettingsSchema.md) file under the keybindings section. Even if that doesn't create parity with VS Code keybindings, it would be helpful for users creating keybindings.
claunia commented 2026-01-30 23:45:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 13, 2020):

:tada:This issue was addressed in #4392, which has now been successfully released as Windows Terminal Preview v0.9.433.0.🎉

Handy links:

@ghost commented on GitHub (Feb 13, 2020): :tada:This issue was addressed in #4392, which has now been successfully released as `Windows Terminal Preview v0.9.433.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.9.433.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?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 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#4375
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?