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

Quake mode hot-key stops working after a while. Restart of terminal fixes it #14127

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

Originally created by @aclinick on GitHub (Jun 4, 2021).

Windows Terminal version (or Windows build number)

1.9.1523.0

Other Software

No response

Steps to reproduce

Run terminal preview. leave it in the background. Go do something else for a while - say 30 mins. Hit Win-` and notice how the quake sweetness has been obliterated (by a BFG perhaps?) Restart terminal and quake goodness is back

Expected Behavior

quake mode all the time....

Actual Behavior

no quake sweetness

Originally created by @aclinick on GitHub (Jun 4, 2021). ### Windows Terminal version (or Windows build number) 1.9.1523.0 ### Other Software _No response_ ### Steps to reproduce Run terminal preview. leave it in the background. Go do something else for a while - say 30 mins. Hit Win-` and notice how the quake sweetness has been obliterated (by a BFG perhaps?) Restart terminal and quake goodness is back ### Expected Behavior quake mode all the time.... ### Actual Behavior no quake sweetness
claunia commented 2026-01-31 04:01:44 +00:00
Author
Owner
Copy Link

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

Well, that's definitely not expected. I'm assuming "do something else for 30 minutes" is basically just the same as "something causes the keybinding to stop working". As long as the Terminal is running, the keybinding should work. We never unregister the hotkey (except on a settings reload), so there's no reason that the global hotkey should ever become unbound.

I'm not sure what kind of tracing we could get that would be valuable here. I suppose we could add tracing for when we do get a hotkey message, but that would only really tell us if the hotkey was pressed, but we decided not to open an instance. I'm more worried that this is "we never got the hotkey message".

I'd welcome other input on this topic - as is, I'm not sure how to investigate this further.

@zadjii-msft commented on GitHub (Jul 6, 2021): Well, that's definitely not expected. I'm assuming "do something else for 30 minutes" is basically just the same as "something causes the keybinding to stop working". As long as the Terminal is running, the keybinding _should_ work. We never unregister the hotkey (except on a settings reload), so there's no reason that the global hotkey should ever become unbound. I'm not sure what kind of tracing we could get that would be valuable here. I suppose we could add tracing for when we _do_ get a hotkey message, but that would only really tell us if the hotkey was pressed, but we decided not to open an instance. I'm more worried that this is "we never got the hotkey message". I'd welcome other input on this topic - as is, I'm not sure how to investigate this further.
claunia commented 2026-01-31 04:01:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 2, 2022):

@aclinick You still seeing this? We haven't really had any other reports of this, so I suspect it was just an intermittent issue on your machine. We might have some logging you can do if it is still happening with relative frequency.

@zadjii-msft commented on GitHub (Feb 2, 2022): @aclinick You still seeing this? We haven't really had any other reports of this, so I suspect it was just an intermittent issue on your machine. We might have some logging you can do if it is still happening with relative frequency.
claunia commented 2026-01-31 04:01:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 6, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Feb 6, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Area-Remoting Issue-Bug Needs-Author-Feedback Needs-Repro Needs-Tag-Fix No-Recent-Activity Priority-3 Product-Terminal
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#14127
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?