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

Add option to switch to last active, i.e. most recent, tab #18012

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

Originally created by @vertigo220 on GitHub (Jul 23, 2022).

Description of the new feature/enhancement

As the title says. Currently can go to previous, next, and last tab, as well as directly to any one of the first several, but can't alternate between two. This is the standard behavior of Ctrl+Tab in many other applications (browsers, Notepad++, etc) and it would be nice to have the same ability here.

Proposed technical implementation details (optional)

Originally created by @vertigo220 on GitHub (Jul 23, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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). --> As the title says. Currently can go to previous, next, and last tab, as well as directly to any one of the first several, but can't alternate between two. This is the standard behavior of Ctrl+Tab in many other applications (browsers, Notepad++, etc) and it would be nice to have the same ability here. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-QuestionResolution-AnsweredResolution-Duplicate labels 2026-01-31 06:01:10 +00:00
claunia commented 2026-01-31 06:01:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 23, 2022):

Perhaps you're looking for "tabSwitcherMode": "mru" - on the action, or even just set globally/?

@zadjii-msft commented on GitHub (Jul 23, 2022): Perhaps you're looking for `"tabSwitcherMode": "mru"` - [on the action](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#open-next-tab), or even just [set globally](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/interaction#tab-switcher-interface-style)/?
claunia commented 2026-01-31 06:01:11 +00:00
Author
Owner
Copy Link

@vertigo220 commented on GitHub (Jul 24, 2022):

Yes, thank you, changing that to mru was indeed the solution I was looking for. I suppose this is a case of just not looking deep enough for the solution but, to be fair, there was nothing in the settings either to help point me in the right direction or to even indicate that such a thing was possible. I realize this is a program meant for advanced users, but I still feel guidance is always helpful both to make things easier for the user and to help prevent issues like these.

I'd suggest starting with adding a prominent message at the top of the actions page (and perhaps all pertinent pages) notifying the user that the actions can be further modified by editing the JSON file and providing a link to https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions (or the appropriate URL for each settings page). This may very well have been enough to tell me the option I'm looking for doesn't exist in settings, but maybe I can manually set it that way.

To take it a step further and help even more, each action could have a link to the specific part of that URL pertinent to that action, e.g. "Next tab" and "Previous tab" could have a link to https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#open-next-tab and https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#open-previous-tab, respectively, and/or show the various options ("mru", "inOrder", "disabled" in this case) in a tooltip or on the right side in the empty space there, and maybe even in a dropbox in the edit mode to automatically change it in the JSON from there. This all would admittedly be a fair amount of work and not really necessary, as even just pointing users in the right direction will be a big help. For example, now that I know this, I know where to look to see if I can do something and how to do it if it's an available option, which will make a big difference, but there may still be times I, or others, might just not see something that looks like what I want or it might be helpful to be able to see at a glance what the options actually are. That all said, this may not even apply to most of the settings, and may not be very useful at all for all but a few of them, and is just me thinking out loud based on being new to Terminal, whereas those who are more familiar with it may very well recognize that fact as may I once I use it more, but I just wanted to offer my thoughts in case they're helpful.

@vertigo220 commented on GitHub (Jul 24, 2022): Yes, thank you, changing that to mru was indeed the solution I was looking for. I suppose this is a case of just not looking deep enough for the solution but, to be fair, there was nothing in the settings either to help point me in the right direction or to even indicate that such a thing was possible. I realize this is a program meant for advanced users, but I still feel guidance is always helpful both to make things easier for the user and to help prevent issues like these. I'd suggest starting with adding a prominent message at the top of the actions page (and perhaps all pertinent pages) notifying the user that the actions can be further modified by editing the JSON file and providing a link to https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions (or the appropriate URL for each settings page). This may very well have been enough to tell me the option I'm looking for doesn't exist in settings, but maybe I can manually set it that way. To take it a step further and help even more, each action could have a link to the specific part of that URL pertinent to that action, e.g. "Next tab" and "Previous tab" could have a link to https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#open-next-tab and https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#open-previous-tab, respectively, and/or show the various options ("mru", "inOrder", "disabled" in this case) in a tooltip or on the right side in the empty space there, and maybe even in a dropbox in the edit mode to automatically change it in the JSON from there. This all would admittedly be a fair amount of work and not really necessary, as even just pointing users in the right direction will be a big help. For example, now that I know this, I know where to look to see if I can do something and how to do it if it's an available option, which will make a big difference, but there may still be times I, or others, might just not see something that looks like what I want or it might be helpful to be able to see at a glance what the options actually are. That all said, this may not even apply to most of the settings, and may not be very useful at all for all but a few of them, and is just me thinking out loud based on being new to Terminal, whereas those who are more familiar with it may very well recognize that fact as may I once I use it more, but I just wanted to offer my thoughts in case they're helpful.
claunia commented 2026-01-31 06:01:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2022):

Those are some good suggestions. Overall, our goal with the Actions page is to enable all the properties of an action to be customizable there. It's just a little bit more engineering time than we have the resources for at the moment. I think we're tracking that broadly in some combination of #12388, #10000, #6900.

FWIW, the global setting is available on the Interaction page of the SUI:

image

I think I'm gonna tentatively call this a /dupe of #6900. We'd probably accept a smaller PR for just adding a link to the docs,. Ultimately, the goal is to just redo most of that page.

@zadjii-msft commented on GitHub (Jul 25, 2022): Those are some good suggestions. Overall, our goal with the Actions page is to enable all the properties of an action to be customizable there. It's just a little bit more engineering time than we have the resources for at the moment. I think we're tracking that broadly in some combination of #12388, #10000, #6900. FWIW, the global setting is available on the Interaction page of the SUI: ![image](https://user-images.githubusercontent.com/18356694/180799778-27ee6434-9161-4406-be33-66c442c2a64f.png) I think I'm gonna tentatively call this a /dupe of #6900. We'd probably accept a smaller PR for just adding a link to the docs,. Ultimately, the goal is to just redo most of that page.
claunia commented 2026-01-31 06:01:11 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 25, 2022):

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 (Jul 25, 2022): 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!
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-Question Resolution-Answered 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#18012
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?