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

Feature Request: Add nextPane and prevPane keybindings #4016

New Issue
Closed
opened 2026-01-30 23:35:56 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 23:35:56 +00:00
Owner
Copy Link

Originally created by @moswald on GitHub (Sep 24, 2019).

There's nextTab and prevTab, but since I work in a single-tab, multi-pane environment, those keybindings do nothing for me. How about being able to bind ctrl+tab to nextPanel?

(Would fit in nicely with the rest of #1000 .)

Edit: I can't believe I typoed that last nextPanel as nextTab, making the sentence and request completely nonsensical. :D

Originally created by @moswald on GitHub (Sep 24, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> There's `nextTab` and `prevTab`, but since I work in a single-tab, multi-pane environment, those keybindings do nothing for me. How about being able to bind `ctrl+tab` to `nextPanel`? (Would fit in nicely with the rest of #1000 .) _Edit: I can't believe I typoed that last `nextPanel` as `nextTab`, making the sentence and request completely nonsensical._ :D
claunia commented 2026-01-30 23:35:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 24, 2019):

As of #1910, you can move the focus between panes "directionally", with moveFocus{Up|Down|Left|Right}.

For example:

            { "keys": ["alt+left"], "command": "moveFocusLeft" },
            { "keys": ["alt+right"], "command": "moveFocusRight" },
            { "keys": ["alt+up"], "command": "moveFocusUp" },
            { "keys": ["alt+down"], "command": "moveFocusDown" },

I suppose though there's also room for moving focus "in order" or "in MRU order" through panes as well. MRU order makes sense, but I'm not really sure how "in order" would work

I'm going to leave this open because this makes sense as a potential feature, though I believe that #1910 will probably satisfy your needs.

@zadjii-msft commented on GitHub (Sep 24, 2019): As of #1910, you can move the focus between panes "directionally", with `moveFocus{Up|Down|Left|Right}`. For example: ```json { "keys": ["alt+left"], "command": "moveFocusLeft" }, { "keys": ["alt+right"], "command": "moveFocusRight" }, { "keys": ["alt+up"], "command": "moveFocusUp" }, { "keys": ["alt+down"], "command": "moveFocusDown" }, ``` I suppose though there's also room for moving focus "in order" or "in MRU order" through panes as well. MRU order makes sense, but I'm not really sure how "in order" would work I'm going to leave this open because this makes sense as a potential feature, though I believe that #1910 will probably satisfy your needs.
claunia commented 2026-01-30 23:35:57 +00:00
Author
Owner
Copy Link

@moswald commented on GitHub (Sep 24, 2019):

Yeah, I'm using the current moveFocus bindings, but they're just not as natural as the ctrl+tab muscle memory I've built up using other apps. I usually switch between just two tabs so MRU would work great, but "in order" could be implemented by remembering the order in which tabs were created.

@moswald commented on GitHub (Sep 24, 2019): Yeah, I'm using the current `moveFocus` bindings, but they're just not as natural as the `ctrl+tab` muscle memory I've built up using other apps. I usually switch between just two tabs so MRU would work great, but "in order" could be implemented by remembering the order in which tabs were created.
claunia commented 2026-01-30 23:35:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 8, 2019):

Yanking the triage tag on this one, since it's a worthwhile thing we should probably have. "Backlog" status stays!

@DHowett-MSFT commented on GitHub (Oct 8, 2019): Yanking the triage tag on this one, since it's a worthwhile thing we should probably have. "Backlog" status stays!
claunia commented 2026-01-30 23:35:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2020):

From @mfeiertag in #7194

New panes get assigned increasing IDs.
{ "command": { "action": "moveFocus", "direction": "next" }, "keys": "ctrl+alt+tab" }
focuses the pane with the next ID
{ "command": { "action": "moveFocus", "direction": "prev" }, "keys": "ctrl+alt+shift+tab" }
focuses the pane with the previous ID

IDs could be in order of creation or in order of last used.
Property Necessity Type Default Description
paneCycleMode Optional String created Defines the order of panes when cycling. Possible values: created or lastUsed

Related to #5803 and #5464
Similar to #4692

Example (pane in focus bold):

Single Pane:
| 1 |
Duplicate pane:
| 1 | | 2 |
Pressing ctrl+alt+tab:
| 1 | | 2 |
Duplicate Pane 1, than pane 2:
| 1 | | 2 |
| 3 | | 4 |
Pressing ctrl+alt+tab would go to pane 1:
| 1 | | 2 |
| 3 | | 4 |
Pressing ctrl+alt+shift+tab would go back to pane 4:
| 1 | | 2 |
| 3 | | 4 |
Pressing ctrl+alt+shift+tab again would go to pane 3:
| 1 | | 2 |
| 3 | | 4 |

@zadjii-msft commented on GitHub (Aug 5, 2020): From @mfeiertag in #7194 > New panes get assigned increasing IDs. > `{ "command": { "action": "moveFocus", "direction": "next" }, "keys": "ctrl+alt+tab" }` > focuses the pane with the next ID > `{ "command": { "action": "moveFocus", "direction": "prev" }, "keys": "ctrl+alt+shift+tab" }` > focuses the pane with the previous ID > > IDs could be in order of creation or in order of last used. > Property Necessity Type Default Description > `paneCycleMode` Optional String `created` Defines the order of panes when cycling. Possible values: `created` or `lastUsed` > > Related to #5803 and #5464 > Similar to #4692 > ### Example (pane in focus bold): > > Single Pane: > | **1** | > Duplicate pane: > | 1 | | **2** | > Pressing ctrl+alt+tab: > | **1** | | 2 | > Duplicate Pane 1, than pane 2: > | 1 | | 2 | > | 3 | | **4** | > Pressing ctrl+alt+tab would go to pane 1: > | **1** | | 2 | > | 3 | | 4 | > Pressing ctrl+alt+shift+tab would go back to pane 4: > | 1 | | 2 | > | 3 | | **4** | > Pressing ctrl+alt+shift+tab again would go to pane 3: > | 1 | | 2 | > | **3** | | 4 |
claunia commented 2026-01-30 23:35:58 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 11, 2020):

moveFocus with direction: previous will be how you do this.

@DHowett commented on GitHub (Dec 11, 2020): `moveFocus` with `direction: previous` will be how you do this.
claunia commented 2026-01-30 23:35:58 +00:00
Author
Owner
Copy Link

@Rosefield commented on GitHub (Jul 29, 2021):

This item seems incomplete, specifically the next portion is missing from the current implementation and the linked spec. To me the idea of having the "in order" style cycling is important (equivalent to just cyclically alt-tabbing between panes) that lets me get to any pane through one keybinding. The "in order" order can be fairly arbitrary (so long as it is consistent), but just iterating through the tree leaves from first-leaf to last-leaf seems reasonable.

Also, the current implementation of the previous movement seems tangential to the "in order backwards" version, in that it only cycles between two panes. e.g. if you have 3 panes, 1| 2 | 3, and you go from 2 to 3, pressing previous will go to 2, then pressing previous will go back to 3 again, with no way to go back to 1. This can be separately useful, but seems to be solving a different feature request.

I would be happy to implement the "in order" next/previous version, but I'm not sure if that goes against the grand plan.

@Rosefield commented on GitHub (Jul 29, 2021): This item seems incomplete, specifically the `next` portion is missing from the current implementation and the linked spec. To me the idea of having the "in order" style cycling is important (equivalent to just cyclically alt-tabbing between panes) that lets me get to any pane through one keybinding. The "in order" order can be fairly arbitrary (so long as it is consistent), but just iterating through the tree leaves from first-leaf to last-leaf seems reasonable. Also, the current implementation of the `previous` movement seems tangential to the "in order backwards" version, in that it only cycles between two panes. e.g. if you have 3 panes, 1| 2 | 3, and you go from 2 to 3, pressing previous will go to 2, then pressing previous will go back to 3 again, with no way to go back to 1. This can be separately useful, but seems to be solving a different feature request. I would be happy to implement the "in order" next/previous version, but I'm not sure if that goes against the grand plan.
claunia commented 2026-01-30 23:35:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 3, 2021):

You know, that's a fair point. We never did come up with an in-order traversal method - that was seemingly lost part of the discussion. I think we got so focused on the MRU previous element, the in-order bit was lost.

I'll bring this up in team sync. See what other folks think. Thanks for bringing this up!

@zadjii-msft commented on GitHub (Aug 3, 2021): You know, that's a fair point. We never did come up with an in-order traversal method - that was seemingly lost part of the discussion. I think we got so focused on the MRU previous element, the in-order bit was lost. I'll bring this up in team sync. See what other folks think. Thanks for bringing this up!
claunia commented 2026-01-30 23:35:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 9, 2021):

After discussion, yea, we totally forgot about the inOrder version of this. "moveFocus": "nextInOrder" and "moveFocus": "previousInOrder" seemed like they were likely candidates for the param to mean "take me to ++paneId" / "take me to --paneId".

I'll move this to a new issue. Thanks for keeping us honest!

@zadjii-msft commented on GitHub (Aug 9, 2021): After discussion, yea, we totally forgot about the inOrder version of this. `"moveFocus": "nextInOrder"` and `"moveFocus": "previousInOrder"` seemed like they were likely candidates for the param to mean "take me to ++paneId" / "take me to --paneId". I'll move this to a new issue. Thanks for keeping us honest!
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-UserInterface Help Wanted Issue-Task 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#4016
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?