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 hotkey does not toggle window visibility #15514

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

Originally created by @Rosefield on GitHub (Oct 11, 2021).

Windows Terminal version (or Windows build number)

1.11.2421

Other Software

W10 19042.1237

Steps to reproduce

  • press the quake mode hotkey "win+`" to summon the quake window,
  • while the quake window is open press again and observe that a new tab is created instead of toggling visibility.

Expected Behavior

The quake window should be summoned, but a new tab should not be created. Additionally if the window is already open it should be hidden on the next press.

Actual Behavior

Each time win+sc(41) is pressed a new tab is added to the quake window instead of toggling visibility.

My settings are here: https://gist.github.com/Rosefield/b89372ee1fbd48c10dd1b3586525e18b although I haven't made any modification to the quake default hotkey.

Originally created by @Rosefield on GitHub (Oct 11, 2021). ### Windows Terminal version (or Windows build number) 1.11.2421 ### Other Software W10 19042.1237 ### Steps to reproduce - press the quake mode hotkey "win+`" to summon the quake window, - while the quake window is open press again and observe that a new tab is created instead of toggling visibility. ### Expected Behavior The quake window should be summoned, but a new tab should not be created. Additionally if the window is already open it should be hidden on the next press. ### Actual Behavior Each time `win+sc(41)` is pressed a new tab is added to the quake window instead of toggling visibility. My settings are here: https://gist.github.com/Rosefield/b89372ee1fbd48c10dd1b3586525e18b although I haven't made any modification to the quake default hotkey.
claunia commented 2026-01-31 04:40:49 +00:00
Author
Owner
Copy Link

@Rosefield commented on GitHub (Oct 13, 2021):

Looks like my terminal updated to 1.11.2731 and I am no longer seeing this, although I don't see a fix mentioned in the release notes 🤷. It is still broken on my other computer that hasn't updated yet.

@Rosefield commented on GitHub (Oct 13, 2021): Looks like my terminal updated to 1.11.2731 and I am no longer seeing this, although I don't see a fix mentioned in the release notes :shrug:. It is still broken on my other computer that hasn't updated yet.
claunia commented 2026-01-31 04:40:50 +00:00
Author
Owner
Copy Link

@Rosefield commented on GitHub (Oct 13, 2021):

I notice that on the computer where this is still broken the quake window has id 1, and even after closing all of the tabs on the quake window and then pressing the hotkey again the new window still has id 1. Perhaps the monarch got into some corrupted state?

@Rosefield commented on GitHub (Oct 13, 2021): I notice that on the computer where this is still broken the quake window has id `1`, and even after closing all of the tabs on the quake window and then pressing the hotkey again the new window still has id `1`. Perhaps the monarch got into some corrupted state?
claunia commented 2026-01-31 04:40:50 +00:00
Author
Owner
Copy Link

@FaustinCarter commented on GitHub (Nov 2, 2021):

I'm having the same exact issue on 1.10.2714.0. Upgrading to Version: 1.11.2921.0 fixed it.

@FaustinCarter commented on GitHub (Nov 2, 2021): I'm having the same exact issue on 1.10.2714.0. Upgrading to Version: 1.11.2921.0 fixed it.
claunia commented 2026-01-31 04:40:50 +00:00
Author
Owner
Copy Link

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

Sorry I didn't see this one sooner!

I notice that on the computer where this is still broken the quake window has id 1, and even after closing all of the tabs on the quake window and then pressing the hotkey again the new window still has id 1. Perhaps the monarch got into some corrupted state?

That's the best guess I'd have.

@Rosefield any chance you're still seeing this? (I know the chances are probably slim). If it's still happening then maybe we can try debugging what's going on. Otherwise I think we just have to leave our ears open to hear if this happens again, and what we can do to try and repro it.

@zadjii-msft commented on GitHub (Nov 3, 2021): Sorry I didn't see this one sooner! > I notice that on the computer where this is still broken the quake window has id `1`, and even after closing all of the tabs on the quake window and then pressing the hotkey again the new window still has id `1`. Perhaps the monarch got into some corrupted state? That's the best guess I'd have. @Rosefield any chance you're still seeing this? (I know the chances are probably slim). If it's still happening then maybe we can try debugging what's going on. Otherwise I think we just have to leave our ears open to hear if this happens again, and what we can do to try and repro it.
claunia commented 2026-01-31 04:40:50 +00:00
Author
Owner
Copy Link

@Rosefield commented on GitHub (Nov 3, 2021):

"Unfortunately" I am not, it probably went away with an update/computer restart. It was curious that it happened on both of my computers at the same time before. Quake mode isn't a feature I normally use, but if I see it again I'll try to capture more diagnostics.

@Rosefield commented on GitHub (Nov 3, 2021): "Unfortunately" I am not, it probably went away with an update/computer restart. It was curious that it happened on both of my computers at the same time before. Quake mode isn't a feature I normally use, but if I see it again I'll try to capture more diagnostics.
claunia commented 2026-01-31 04:40:50 +00:00
Author
Owner
Copy Link

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

Okay I'm just gonna cautiously close for now, and obviously we can reopen if needed

@zadjii-msft commented on GitHub (Nov 3, 2021): Okay I'm just gonna cautiously close for now, and obviously we can reopen if needed
claunia commented 2026-01-31 04:40:51 +00:00
Author
Owner
Copy Link

@mave-panda commented on GitHub (Dec 19, 2022):

This behaviour seems to be back in Windows Terminal Preview
Version: 1.16.3463.0

@mave-panda commented on GitHub (Dec 19, 2022): This behaviour seems to be back in Windows Terminal Preview Version: 1.16.3463.0
claunia commented 2026-01-31 04:40:51 +00:00
Author
Owner
Copy Link

@cypherfunc commented on GitHub (Oct 2, 2023):

Seems to be back again? I'm running Windows Terminal v1.17.11461.0

(Also, clicking outside the quake terminal doesn't collapse it either, but I'm not sure whether that's intended behavior.)

@cypherfunc commented on GitHub (Oct 2, 2023): Seems to be back again? I'm running Windows Terminal v1.17.11461.0 (Also, clicking outside the quake terminal doesn't collapse it either, but I'm not sure whether that's intended behavior.)
claunia commented 2026-01-31 04:40:51 +00:00
Author
Owner
Copy Link

@cypherfunc commented on GitHub (Oct 13, 2023):

Not sure how or why, but this seems to be fixed. I have gotten a Windows update, but I'm still on Terminal v1.17.11461.0 🤷‍♂️

@cypherfunc commented on GitHub (Oct 13, 2023): Not sure how or why, but this seems to be fixed. I have gotten a Windows update, but I'm still on Terminal v1.17.11461.0 🤷‍♂️
claunia commented 2026-01-31 04:40:51 +00:00
Author
Owner
Copy Link

@shrirammaiya commented on GitHub (Oct 19, 2023):

I had the same issue (v1.19.2628.0). It got fixed when I repaired the app using the default Windows tool:

Settings>Apps>Apps and Features> Terminal Preview > Advanced Options > Repair

No clue why the issue was occuring though, but this fixed it for me.

@shrirammaiya commented on GitHub (Oct 19, 2023): I had the same issue (v1.19.2628.0). It got fixed when I repaired the app using the default Windows tool: **Settings>Apps>Apps and Features> Terminal Preview > Advanced Options > Repair** No clue why the issue was occuring though, but this fixed it for me.
claunia commented 2026-01-31 04:40:51 +00:00
Author
Owner
Copy Link

@quadrinex commented on GitHub (May 25, 2025):

👍 +1
This Issue still happen, pls reopen to find a proper solution to it.

@quadrinex commented on GitHub (May 25, 2025): 👍 +1 This Issue still happen, pls reopen to find a proper solution to it.
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 Needs-Attention Needs-Tag-Fix Needs-Triage 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#15514
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?