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

New hotkey bindings are not reflected in dropdown UI #11406

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

Originally created by @daniel-norris on GitHub (Nov 14, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19042.630]
Windows Terminal version (if applicable): 1.4.3141.0

Steps to reproduce

Open settings.json in your text editor and follow the instructions in the documentation (found here) to change the default bindings. In the screenshots below I have changed the bindings from ctrl+shift+1, ctrl+shift+2, etc... to alt+1.

Save and then restart your Windows Terminal client and use the default hotkey (ctrl+shift+space) to access the dropdown or click the caret to open.

Expected behavior

The dropdown should accurately reflect the new hotkeys set in settings.json for new tabs.

Actual behavior

After the settings.json file is updated and hotkeys are set for actions to open a new tab in a desired profile, the dropdown UI does not accurately reflect the new bindings.

image

image

Originally created by @daniel-norris on GitHub (Nov 14, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19042.630] Windows Terminal version (if applicable): 1.4.3141.0 ``` # Steps to reproduce Open `settings.json` in your text editor and follow the instructions in the documentation (found [here](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions)) to change the default bindings. In the screenshots below I have changed the bindings from `ctrl+shift+1`, `ctrl+shift+2`, etc... to `alt+1`. Save and then restart your Windows Terminal client and use the default hotkey (`ctrl+shift+space`) to access the dropdown or click the caret to open. # Expected behavior The dropdown should accurately reflect the new hotkeys set in `settings.json` for new tabs. # Actual behavior After the `settings.json` file is updated and hotkeys are set for actions to open a new tab in a desired profile, the dropdown UI does not accurately reflect the new bindings. ![image](https://user-images.githubusercontent.com/58988735/99149851-737e5900-2688-11eb-96b6-8b0edd80b242.png) ![image](https://user-images.githubusercontent.com/58988735/99149862-8002b180-2688-11eb-8956-97c33a3bba49.png)
claunia added the Resolution-Duplicate label 2026-01-31 02:46:43 +00:00
claunia commented 2026-01-31 02:46:43 +00:00
Author
Owner
Copy Link

@daniel-norris commented on GitHub (Nov 14, 2020):

I would love to have a go at helping to produce a fix for this if possible?

@daniel-norris commented on GitHub (Nov 14, 2020): I would love to have a go at helping to produce a fix for this if possible?
claunia commented 2026-01-31 02:46:44 +00:00
Author
Owner
Copy Link

@LuanVSO commented on GitHub (Nov 15, 2020):

you need to "unbound" the default key bindings, otherwise they are still bound to the same action adding:

{"keys": "ctrl+shift+1", "command": "unbound"},

in the key bindings should do the trick.
although maybe that menu should prefer to show the user key binding if it is set?

@LuanVSO commented on GitHub (Nov 15, 2020): you need to "unbound" the default key bindings, otherwise they are still bound to the same action adding: ```Json {"keys": "ctrl+shift+1", "command": "unbound"}, ``` in the key bindings should do the trick. although maybe that menu should prefer to show the user key binding if it is set?
claunia commented 2026-01-31 02:46:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 15, 2020):

Thanks for the report! This is a /dupe of #2991 😄 and if you're interested in working on it, there should be more info over there.

@DHowett commented on GitHub (Nov 15, 2020): Thanks for the report! This is a /dupe of #2991 :smile: and if you're interested in working on it, there should be more info over there.
claunia commented 2026-01-31 02:46:44 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 15, 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 (Nov 15, 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.
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 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#11406
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?