Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
storopchanin opened this issue Oct 22, 2020 · 3 comments
Closed
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@storopchanin
Copy link

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)

@storopchanin storopchanin added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 22, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 22, 2020
@DHowett
Copy link
Member

DHowett commented Oct 22, 2020

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

@DHowett DHowett closed this as completed Oct 22, 2020
@zadjii-msft
Copy link
Member

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!

@ghost
Copy link

ghost commented 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 ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants