Change current terminal behavior for "nextTab" and "prevTab" commands #11128

Closed
opened 2026-01-31 02:39:21 +00:00 by claunia · 3 comments
Owner

Originally created by @storopchanin on GitHub (Oct 22, 2020).

Description of the new feature/enhancement

Currently when you press hotkeys associated with "nextTab" and "prevTab" commands the following carousel appears in Windows Terminal:
image
The carousel above doesn't provide any useful information about what is happening in your tabs.

Proposed technical implementation details

Please implement standard "nextTab" and "prevTab" behavior: when you press associated hotkeys and program immediately switches to next / previous tab, e.g. Google Chrome (open multiple tabs and use hotkeys Ctrl + PgUp / Ctrl + PgDn)

Originally created by @storopchanin on GitHub (Oct 22, 2020). # Description of the new feature/enhancement Currently when you press hotkeys associated with "nextTab" and "prevTab" commands the following carousel appears in Windows Terminal: ![image](https://user-images.githubusercontent.com/25746391/96904518-82ae2480-1497-11eb-847d-05c53e468b1a.png) The carousel above doesn't provide any useful information about what is happening in your tabs. # Proposed technical implementation details Please implement standard "nextTab" and "prevTab" behavior: when you press associated hotkeys and program immediately switches to next / previous tab, e.g. Google Chrome (open multiple tabs and use hotkeys Ctrl + PgUp / Ctrl + PgDn)
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:39:21 +00:00
Author
Owner

@DHowett commented on GitHub (Oct 22, 2020):

You can disable the new tab switching experience by setting useTabSwitcher to false in your settings file.

@DHowett commented on GitHub (Oct 22, 2020): You can disable the new tab switching experience by setting `useTabSwitcher` to `false` in your settings file.
Author
Owner

@zadjii-msft commented on GitHub (Oct 22, 2020):

Also, this is actually already fixed in the main branch, and should be heading out to users soontm.

This was originally being tracked over in /dup #7409

This was fixed in PR #7796.

If you subscribe to either of those threads, you'll be notified by the bot when an update is pushed to the store that contains that change. Thanks!

@zadjii-msft commented on GitHub (Oct 22, 2020): Also, this is actually already fixed in the main branch, and should be heading out to users soon<sup>tm</sup>. This was originally being tracked over in /dup #7409 This was fixed in PR #7796. If you subscribe to either of those threads, you'll be notified by the bot when an update is pushed to the store that contains that change. Thanks!
Author
Owner

@ghost commented on GitHub (Oct 22, 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 (Oct 22, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11128