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

Key combination win+enter not working for global summon #14719

New Issue
Closed
opened 2026-01-31 04:17:42 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:17:42 +00:00
Owner
Copy Link

Originally created by @Areyus on GitHub (Jul 29, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

No response

Steps to reproduce

Set "win+enter" as keycode for the globalSummon action in the config and press the buttons. This is the exact line I have in settings.json:

{ "command": { "action": "globalSummon", "toggleVisibility": true }, "keys": "win+enter"},

Expected Behavior

globalSummon works like it does with other key combinations.

Actual Behavior

Nothing happens. From what I understood, you cannot bind globalSummon to key combinations that are already used by Windows default shortcuts, but I could not find any action bound to that combination, neither by testing nor by searching online.

Originally created by @Areyus on GitHub (Jul 29, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software _No response_ ### Steps to reproduce Set "win+enter" as keycode for the globalSummon action in the config and press the buttons. This is the exact line I have in settings.json: ``` { "command": { "action": "globalSummon", "toggleVisibility": true }, "keys": "win+enter"}, ``` ### Expected Behavior globalSummon works like it does with other key combinations. ### Actual Behavior Nothing happens. From what I understood, you cannot bind globalSummon to key combinations that are already used by Windows default shortcuts, but I could not find any action bound to that combination, neither by testing nor by searching online.
claunia added the Resolution-Duplicate label 2026-01-31 04:17:42 +00:00
claunia commented 2026-01-31 04:17:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 29, 2021):

Thanks for the report! I'm afraid that Win+Enter might be one of those keystrokes that's reserved by the system for some reason. I'm not sure why, but we never get that keystroke. There are more details in #4760.

If we ever get to the root cause of that issue, we'll probably follow up in that thread. Thanks!

/dup #4760

@zadjii-msft commented on GitHub (Jul 29, 2021): Thanks for the report! I'm afraid that <kbd>Win+Enter</kbd> might be one of those keystrokes that's reserved by the system for some reason. I'm not sure why, but we _never_ get that keystroke. There are more details in #4760. If we ever get to the root cause of that issue, we'll probably follow up in that thread. Thanks! /dup #4760
claunia commented 2026-01-31 04:17:43 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 29, 2021):

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 (Jul 29, 2021): 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#14719
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?