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

Set panes keybindings by default #4952

New Issue
Closed
opened 2026-01-31 00:01:27 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:01:27 +00:00
Owner
Copy Link

Originally created by @cinnamon-msft on GitHub (Nov 12, 2019).

Originally assigned to: @cinnamon-msft on GitHub.

Description of the new feature/enhancement

Include panes keybindings by default

Proposed technical implementation details (optional)

Current keybinding suggestion:

		{ "command": "splitHorizontal", "keys": [ "alt+shift+-" ] },
        { "command": "splitVertical", "keys": [ "alt+shift+plus" ] },
        { "command": { "action": "moveFocus", "direction":"down" }, "keys": [ "alt+down" ] },
        { "command": { "action": "moveFocus", "direction":"left" }, "keys": [ "alt+left" ] },
        { "command": { "action": "moveFocus", "direction":"right" }, "keys": [ "alt+right" ] },
        { "command": { "action": "moveFocus", "direction":"up" }, "keys": [ "alt+up" ] },
        { "command": { "action": "resizePane", "direction":"down" }, "keys": [ "alt+shift+down" ] },
        { "command": { "action": "resizePane", "direction":"left" }, "keys": [ "alt+shift+left" ] },
        { "command": { "action": "resizePane", "direction":"right" }, "keys": [ "alt+shift+right" ] },
        { "command": { "action": "resizePane", "direction":"up" }, "keys": [ "alt+shift+up" ] },
Originally created by @cinnamon-msft on GitHub (Nov 12, 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 Include panes keybindings by default <!-- 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) Current keybinding suggestion: ``` { "command": "splitHorizontal", "keys": [ "alt+shift+-" ] }, { "command": "splitVertical", "keys": [ "alt+shift+plus" ] }, { "command": { "action": "moveFocus", "direction":"down" }, "keys": [ "alt+down" ] }, { "command": { "action": "moveFocus", "direction":"left" }, "keys": [ "alt+left" ] }, { "command": { "action": "moveFocus", "direction":"right" }, "keys": [ "alt+right" ] }, { "command": { "action": "moveFocus", "direction":"up" }, "keys": [ "alt+up" ] }, { "command": { "action": "resizePane", "direction":"down" }, "keys": [ "alt+shift+down" ] }, { "command": { "action": "resizePane", "direction":"left" }, "keys": [ "alt+shift+left" ] }, { "command": { "action": "resizePane", "direction":"right" }, "keys": [ "alt+shift+right" ] }, { "command": { "action": "resizePane", "direction":"up" }, "keys": [ "alt+shift+up" ] }, ```
claunia commented 2026-01-31 00:01:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 12, 2019):

I like this suggestion, because it ties everything related to Panes together with the alt key. Splitting, moving focus, resizing, all done with the alt key in the key chord.

I also like these because these are my current keybindings 😜

EDIT:
Also, people seem to like these
image

@zadjii-msft commented on GitHub (Nov 12, 2019): I like this suggestion, because it ties everything related to Panes together with the <kbd>alt</kbd> key. Splitting, moving focus, resizing, all done with the alt key in the key chord. <sub> I also like these because _these are **my** current keybindings_ 😜 </sub> EDIT: Also, people seem to like these ![image](https://user-images.githubusercontent.com/18356694/68902344-a6041780-06fd-11ea-9410-f7e2d0b9c690.png)
claunia commented 2026-01-31 00:01:29 +00:00
Author
Owner
Copy Link

@egmontkob commented on GitHub (Nov 18, 2019):

Which camp did you guys join according to https://english.stackexchange.com/q/293520 ? :-)

@egmontkob commented on GitHub (Nov 18, 2019): Which camp did you guys join according to https://english.stackexchange.com/q/293520 ? :-)
claunia commented 2026-01-31 00:01:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 18, 2019):

@egmontkob I pretty arbitrarily picked the following:

  • If a Pane is split vertically, the two panes are seperated by a split, as to appear side-by-side. Think [|]
  • If a Pane is split horizontally, the two panes are split by a horizontal separator, and appear above/below one another. Think [-].

The Split(Direction) commands are used to add a separator such that the separator itself is either vertical or horizontal. At least that's the way I interpreted it, though there was some discussion on the matter.

@zadjii-msft commented on GitHub (Nov 18, 2019): @egmontkob I pretty arbitrarily picked the following: > * If a Pane is split vertically, the two panes are seperated by a split, as to appear side-by-side. Think `[|]` > * If a Pane is split horizontally, the two panes are split by a horizontal separator, and appear above/below one another. Think `[-]`. The Split(Direction) commands are used to add a separator such that the separator itself is either vertical or horizontal. At least that's the way I interpreted it, though there was some discussion on the matter.
claunia commented 2026-01-31 00:01:29 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 26, 2019):

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

Handy links:

@ghost commented on GitHub (Nov 26, 2019): :tada:This issue was addressed in #3585, which has now been successfully released as `Windows Terminal Preview v0.7.3291.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.7.3291.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-Input Area-UserInterface 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#4952
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?