starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

WT not respecting new tab index defined in default.json #15130

New Issue
Open
opened 2026-01-31 04:29:24 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:29:24 +00:00
Owner
Copy Link

Originally created by @elsaco on GitHub (Sep 8, 2021).

Windows Terminal version (or Windows build number)

10.0.19043.0 1.9.1942.0

Other Software

No response

Steps to reproduce

  • open a new tab with ctrl+shift+1 for tab index 0
  • open a new tab with ctrl+shift+8 for tab index 7
  • open a new tab with ctrl+shift+9 for tab index 8
  • open a new tab with crtl+shift+0+9 <--this key combination should not be allowed but it opens a new tab

Expected Behavior

New tab to be assigned to the index specified in default.json.

Actual Behavior

New tabs are added sequentially. Using above example when opening a new tab with ctrl+shift+9 it became tab index 1. If crtl+shift+9 is used again tab index 2 is opened. So, crtl+alt+9 will not switch to tab index 8, because there is no such tab index.

crtl+shift+0+9 or any other 1-9 key should not open a new tab when an extra key is added to the combination. In fact, any additional key (numbers + letters) added to crtl+shift+number will open a new tab, i.e crtl+shift+a+1.

Originally created by @elsaco on GitHub (Sep 8, 2021). ### Windows Terminal version (or Windows build number) 10.0.19043.0 1.9.1942.0 ### Other Software _No response_ ### Steps to reproduce - open a new tab with ctrl+shift+1 for tab index 0 - open a new tab with ctrl+shift+8 for tab index 7 - open a new tab with ctrl+shift+9 for tab index 8 - open a new tab with crtl+shift+0+9 <--this key combination should not be allowed but it opens a new tab ### Expected Behavior New tab to be assigned to the index specified in default.json. ### Actual Behavior New tabs are added sequentially. Using above example when opening a new tab with ctrl+shift+9 it became tab index 1. If crtl+shift+9 is used again tab index 2 is opened. So, crtl+alt+9 will not switch to tab index 8, because there is no such tab index. crtl+shift+0+9 or any other 1-9 key should not open a new tab when an extra key is added to the combination. In fact, any additional key (numbers + letters) added to crtl+shift+number will open a new tab, i.e crtl+shift+a+1.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity Product-Terminal Resolution-Answered
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#15130
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?