Mistake in defaults.json skips ctrl+shift+8 #10958

Closed
opened 2026-01-31 02:34:43 +00:00 by claunia · 5 comments
Owner

Originally created by @whorfin on GitHub (Oct 9, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Microsoft Windows [Version 10.0.19041.508]

Windows Terminal version (if applicable): 1.3.2651.0

Any other software?

Steps to reproduce

Alt+Settings to open "defaults.json"
observe the section directly under "newTab":
{ "command": { "action": "newTab", "index": 0 }, "keys": "ctrl+shift+1" },
{ "command": { "action": "newTab", "index": 1 }, "keys": "ctrl+shift+2" },
{ "command": { "action": "newTab", "index": 2 }, "keys": "ctrl+shift+3" },
{ "command": { "action": "newTab", "index": 3 }, "keys": "ctrl+shift+4" },
{ "command": { "action": "newTab", "index": 4 }, "keys": "ctrl+shift+5" },
{ "command": { "action": "newTab", "index": 5 }, "keys": "ctrl+shift+6" },
{ "command": { "action": "newTab", "index": 6 }, "keys": "ctrl+shift+7" },
{ "command": { "action": "newTab", "index": 7 }, "keys": "ctrl+shift+9" },
{ "command": { "action": "newTab", "index": 8 }, "keys": "ctrl+shift+9" },

See anything amiss?
That sure looks like the newTab with index 7 should be "ctrl+shift+8" not 9

Cheers

Originally created by @whorfin on GitHub (Oct 9, 2020). # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Microsoft Windows [Version 10.0.19041.508] Windows Terminal version (if applicable): 1.3.2651.0 Any other software? ``` # Steps to reproduce Alt+Settings to open "defaults.json" observe the section directly under "newTab": { "command": { "action": "newTab", "index": 0 }, "keys": "ctrl+shift+1" }, { "command": { "action": "newTab", "index": 1 }, "keys": "ctrl+shift+2" }, { "command": { "action": "newTab", "index": 2 }, "keys": "ctrl+shift+3" }, { "command": { "action": "newTab", "index": 3 }, "keys": "ctrl+shift+4" }, { "command": { "action": "newTab", "index": 4 }, "keys": "ctrl+shift+5" }, { "command": { "action": "newTab", "index": 5 }, "keys": "ctrl+shift+6" }, { "command": { "action": "newTab", "index": 6 }, "keys": "ctrl+shift+7" }, { "command": { "action": "newTab", "index": 7 }, "keys": "ctrl+shift+9" }, { "command": { "action": "newTab", "index": 8 }, "keys": "ctrl+shift+9" }, See anything amiss? That sure looks like the newTab with index 7 should be "ctrl+shift+8" not 9 Cheers
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 02:34:44 +00:00
Author
Owner

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

???

This is a snippet from our repository taken today;

image

these bindings haven't changed in months...

Have you seen other files on your machine corrupt themselves?

@DHowett commented on GitHub (Oct 9, 2020): ??? This is a snippet from our repository taken today; ![image](https://user-images.githubusercontent.com/189190/95635035-27644700-0a40-11eb-9f0d-d6b0155cdff7.png) these bindings haven't changed in months... Have you seen other files on your machine corrupt themselves?
Author
Owner

@whorfin commented on GitHub (Oct 9, 2020):

Exciting!
I happen to have a second machine with freshly installed Windows and freshly installed Windows Terminal
...and it shows the defaults.json exactly as you show
So indeed, something went haywire on my machine, or there is some version thing with WT on that machine i need to fix
Whatever the fact, this can't be considered a bug in anything current, so i'll close out and exit stage left...
Cheers

@whorfin commented on GitHub (Oct 9, 2020): Exciting! I happen to have a second machine with freshly installed Windows and freshly installed Windows Terminal ...and it shows the defaults.json exactly as you show So indeed, something went haywire on my machine, or there is some version thing with WT on that machine i need to fix Whatever the fact, this can't be considered a bug in anything current, so i'll close out and exit stage left... Cheers
Author
Owner

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

That's wild! Thanks for checking!

@DHowett commented on GitHub (Oct 9, 2020): That's wild! Thanks for checking!
Author
Owner

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

FYI - terminal doesn't actually read defaults.json and it's all a big lie. It has a copy embedded in TerminalApp.dll (now Microsoft.Terminal.Settings.Model.dll) that it reads, so it doesn't have to do file path lookup/handling/deal with filesystem issues once it's already running. That may lead to a bit more confusion!

@DHowett commented on GitHub (Oct 9, 2020): FYI - terminal doesn't actually read defaults.json and it's all a big lie. It has a copy embedded in TerminalApp.dll (now Microsoft.Terminal.Settings.Model.dll) that it reads, so it doesn't have to do file path lookup/handling/deal with filesystem issues once it's already running. That may lead to a bit more confusion!
Author
Owner

@whorfin commented on GitHub (Oct 9, 2020):

oooh, thanks for the Knowledge!

@whorfin commented on GitHub (Oct 9, 2020): oooh, thanks for the Knowledge!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10958