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

Quake mode not working #14093

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

Originally created by @gnarlygeek on GitHub (Jun 2, 2021).

Windows Terminal version (or Windows build number)

10.0.21390.0 1.9.1445.0

Other Software

NA - Windows hot key issue

Steps to reproduce

Removed existing settings.json file to force create update to the new terminal release.
Win+ generates tone - no quake mode. Edit the new settings.json file - no quake mode found. Add quake mode setting per the documentation - tried both entries - quick and long. Get error on value toCursor - replaced with toCurrent. Save settings.json Win+ still does not load - just a tone.
Edit settings.json and change key sequence to Win+shift+q and save.
Win+shift+q - does not load - same tone sounds.

The prior step confirms that this issue isn't a hot key conflict - I do not have PowerToys installed.

new-settings.zip

Expected Behavior

Quake mode open

Actual Behavior

A tone sounds instead and no screen activity.

Originally created by @gnarlygeek on GitHub (Jun 2, 2021). ### Windows Terminal version (or Windows build number) 10.0.21390.0 1.9.1445.0 ### Other Software NA - Windows hot key issue ### Steps to reproduce Removed existing settings.json file to force create update to the new terminal release. Win+` generates tone - no quake mode. Edit the new settings.json file - no quake mode found. Add quake mode setting per the documentation - tried both entries - quick and long. Get error on value toCursor - replaced with toCurrent. Save settings.json Win+` still does not load - just a tone. Edit settings.json and change key sequence to Win+shift+q and save. Win+shift+q - does not load - same tone sounds. ## The prior step confirms that this issue isn't a hot key conflict - I do not have PowerToys installed. [new-settings.zip](https://github.com/microsoft/terminal/files/6587460/new-settings.zip) ### Expected Behavior Quake mode open ### Actual Behavior A tone sounds instead and no screen activity.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 04:00:42 +00:00
claunia commented 2026-01-31 04:00:43 +00:00
Author
Owner
Copy Link

@gnarlygeek commented on GitHub (Jun 2, 2021):

Sorry about the formatting. I didn't realize the back tick would do that.

@gnarlygeek commented on GitHub (Jun 2, 2021): Sorry about the formatting. I didn't realize the back tick would do that.
claunia commented 2026-01-31 04:00:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 2, 2021):

What happens if you try a key binding that doesn't involve the win key? What about something ridiculous like ctrl+a (obviously this is for testing, don't leave that bound, it'll steal ctrl+a from all apps).

@zadjii-msft commented on GitHub (Jun 2, 2021): What happens if you try a key binding that doesn't involve the <kbd>win</kbd> key? What about something ridiculous like `ctrl+a` (obviously this is for testing, don't leave that bound, it'll steal <kbd>ctrl+a</kbd> from all apps).
claunia commented 2026-01-31 04:00:44 +00:00
Author
Owner
Copy Link

@gnarlygeek commented on GitHub (Jun 3, 2021):

Good suggestion. I tried ctrl+q and ctrl+shift+q - nothing - no sound - nothing.

From: Mike Griese @.>
Sent: Wednesday, June 2, 2021 6:16 PM
To: microsoft/terminal @.>
Cc: Tom Arthur @.>; Author @.>
Subject: Re: [microsoft/terminal] Quake mode not working (#10313)

What happens if you try a key binding that doesn't involve the win key? What about something ridiculous like ctrl+a (obviously this is for testing, don't leave that bound, it'll steal ctrl+a from all apps).

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F10313%23issuecomment-853418758&data=04%7C01%7C%7C5836579f306a440059be08d926140847%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582689747402919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CG1XLVBRguVy0RYhHrOW9WTBzdMvBf1QJ%2BGia6mjeDE%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAELAR3SRLBKODN6CJKKECG3TQ2USZANCNFSM457P3I2Q&data=04%7C01%7C%7C5836579f306a440059be08d926140847%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582689747412916%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=esa7oUPQnigJthf8BsIRV%2FAQNGGLGpEI1BCEvqSwnFs%3D&reserved=0.

@gnarlygeek commented on GitHub (Jun 3, 2021): Good suggestion. I tried ctrl+q and ctrl+shift+q - nothing - no sound - nothing. From: Mike Griese ***@***.***> Sent: Wednesday, June 2, 2021 6:16 PM To: microsoft/terminal ***@***.***> Cc: Tom Arthur ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/terminal] Quake mode not working (#10313) What happens if you try a key binding that doesn't involve the win key? What about something ridiculous like ctrl+a (obviously this is for testing, don't leave that bound, it'll steal ctrl+a from all apps). - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F10313%23issuecomment-853418758&data=04%7C01%7C%7C5836579f306a440059be08d926140847%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582689747402919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CG1XLVBRguVy0RYhHrOW9WTBzdMvBf1QJ%2BGia6mjeDE%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAELAR3SRLBKODN6CJKKECG3TQ2USZANCNFSM457P3I2Q&data=04%7C01%7C%7C5836579f306a440059be08d926140847%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582689747412916%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=esa7oUPQnigJthf8BsIRV%2FAQNGGLGpEI1BCEvqSwnFs%3D&reserved=0>.
claunia commented 2026-01-31 04:00:44 +00:00
Author
Owner
Copy Link

@gnarlygeek commented on GitHub (Jun 3, 2021):

Ok, new development. The issue is in the instructions/documentation. Nowhere does it explicitly mention that Windows Terminal must ALREADY be open before the hot key will work. This is obvious to me now. However it seems that one could also assume that the Terminal team had somehow used a Windows feature to enable the hot key without Terminal running. I will close this issue now, but recommend the usage text for Quake mode explicitly say that Windows Terminal (Preview) must already be open.

@gnarlygeek commented on GitHub (Jun 3, 2021): Ok, new development. The issue is in the instructions/documentation. Nowhere does it explicitly mention that Windows Terminal must ALREADY be open before the hot key will work. This is obvious to me now. However it seems that one could also assume that the Terminal team had somehow used a Windows feature to enable the hot key without Terminal running. I will close this issue now, but recommend the usage text for Quake mode explicitly say that Windows Terminal (Preview) must already be open.
claunia commented 2026-01-31 04:00:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 3, 2021):

Nowhere does it explicitly mention that Windows Terminal must ALREADY be open before the hot key will work.

https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-summon-preview:

  • These key strokes will only work when an instance of the terminal is already running. To launch the terminal automatically on login, see startOnUserLogin.

🤔

@zadjii-msft commented on GitHub (Jun 3, 2021): > Nowhere does it explicitly mention that Windows Terminal must ALREADY be open before the hot key will work. https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-summon-preview: > * These key strokes will only work when an instance of the terminal is already running. To launch the terminal automatically on login, see startOnUserLogin. 🤔
claunia commented 2026-01-31 04:00:44 +00:00
Author
Owner
Copy Link

@gnarlygeek commented on GitHub (Jun 3, 2021):

Ouch! Thanks. I think I will set the launch on login.

From: Mike Griese @.>
Sent: Wednesday, June 2, 2021 7:55 PM
To: microsoft/terminal @.>
Cc: Tom Arthur @.>; State change @.>
Subject: Re: [microsoft/terminal] Quake mode not working (#10313)

Nowhere does it explicitly mention that Windows Terminal must ALREADY be open before the hot key will work.

https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-summon-previewhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fterminal%2Fcustomize-settings%2Factions%23global-summon-preview&data=04%7C01%7C%7Cf3fbcadd65a14c7f0cf008d92621c6f4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582748772483512%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CLEjve5GXSv24YGx23MWWgYlW264wx7pmYg6z6a6SNs%3D&reserved=0:

  • These key strokes will only work when an instance of the terminal is already running. To launch the terminal automatically on login, see startOnUserLogin.

🤔

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F10313%23issuecomment-853455861&data=04%7C01%7C%7Cf3fbcadd65a14c7f0cf008d92621c6f4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582748772493507%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AyxrTjTzZco5goRmBM%2FhisZOH0VtmkMXWocC%2BnCUA%2FY%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAELAR3UBVJFEHXZARGFXTCDTQ3ADXANCNFSM457P3I2Q&data=04%7C01%7C%7Cf3fbcadd65a14c7f0cf008d92621c6f4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582748772493507%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hbG94AA%2F%2BloBu%2FDgEJjujciVTRLMU6%2FarTYuywrH5p8%3D&reserved=0.

@gnarlygeek commented on GitHub (Jun 3, 2021): Ouch! Thanks. I think I will set the launch on login. From: Mike Griese ***@***.***> Sent: Wednesday, June 2, 2021 7:55 PM To: microsoft/terminal ***@***.***> Cc: Tom Arthur ***@***.***>; State change ***@***.***> Subject: Re: [microsoft/terminal] Quake mode not working (#10313) Nowhere does it explicitly mention that Windows Terminal must ALREADY be open before the hot key will work. https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-summon-preview<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fterminal%2Fcustomize-settings%2Factions%23global-summon-preview&data=04%7C01%7C%7Cf3fbcadd65a14c7f0cf008d92621c6f4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582748772483512%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CLEjve5GXSv24YGx23MWWgYlW264wx7pmYg6z6a6SNs%3D&reserved=0>: * These key strokes will only work when an instance of the terminal is already running. To launch the terminal automatically on login, see startOnUserLogin. 🤔 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F10313%23issuecomment-853455861&data=04%7C01%7C%7Cf3fbcadd65a14c7f0cf008d92621c6f4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582748772493507%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AyxrTjTzZco5goRmBM%2FhisZOH0VtmkMXWocC%2BnCUA%2FY%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAELAR3UBVJFEHXZARGFXTCDTQ3ADXANCNFSM457P3I2Q&data=04%7C01%7C%7Cf3fbcadd65a14c7f0cf008d92621c6f4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637582748772493507%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hbG94AA%2F%2BloBu%2FDgEJjujciVTRLMU6%2FarTYuywrH5p8%3D&reserved=0>.
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 Needs-Attention Needs-Tag-Fix Needs-Triage
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#14093
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?