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

Quake mode from the launch #17274

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

Originally created by @NSurtsev on GitHub (Apr 18, 2022).

Windows Terminal version

1.12.10732.0

Windows build number

19044.1645

Other Software

No response

Steps to reproduce

Launch Terminal

Expected Behavior

When we have "Quake mode" ability, I expect to have option to have Quake window when I launch Terminal or at least autoreplace the default window If I use Win+~

Actual Behavior

I launch Terminal, get default Terminal window and I have to press Win+` to get Quake ( window #2), then to system tray and close default Terminal window #1.
And only then it becomes as it should be (but still, name #2 remains for Quake for whatever reason).

Originally created by @NSurtsev on GitHub (Apr 18, 2022). ### Windows Terminal version 1.12.10732.0 ### Windows build number 19044.1645 ### Other Software _No response_ ### Steps to reproduce Launch Terminal ### Expected Behavior When we have "Quake mode" ability, I expect to have option to have Quake window when I launch Terminal or at least autoreplace the default window If I use Win+~ ### Actual Behavior I launch Terminal, get default Terminal window and I have to press Win+` to get Quake ( window #2), then to system tray and close default Terminal window #1. And only then it becomes as it should be (but still, name #2 remains for Quake for whatever reason).
claunia commented 2026-01-31 05:37:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 18, 2022):

This sounds like you're looking for #9996.

You can immediately launch the quake window with wt -w _quake. Or, you should be able to convert an existing window to be the quake window by renaming the window to _quake (with the "Rename window" action in the Command Palette). That of course assumes there isn't an already running quake window, of course.

Does that make sense?

@zadjii-msft commented on GitHub (Apr 18, 2022): This sounds like you're looking for #9996. You can immediately launch the quake window with `wt -w _quake`. Or, you should be able to convert an existing window to be the quake window by renaming the window to `_quake` (with the "Rename window" action in the Command Palette). That of course assumes there isn't an already running quake window, of course. Does that make sense?
claunia commented 2026-01-31 05:37:32 +00:00
Author
Owner
Copy Link

@NSurtsev commented on GitHub (Apr 18, 2022):

This sounds like you're looking for #9996.

You can immediately launch the quake window with wt -w _quake. Or, you should be able to convert an existing window to be the quake window by renaming the window to _quake (with the "Rename window" action in the Command Palette). That of course assumes there isn't an already running quake window, of course.

Does that make sense?

Ok, these options are interesting, but that doesn't actually solve the main issue.
Why should I right commands or doing renames when I should launch Terminal and Quake window should meet me immediately?
(Btw, there should be option in settings to make Quake mode default for launching)
And even if I do not check this potential future option and there is default window opened, I should just press Win+` and this window should become Quake, because I checked "make new instance add to existing window" option in settings (if you do not check it, then it should create separate Quake window like it already does now)

@NSurtsev commented on GitHub (Apr 18, 2022): > This sounds like you're looking for #9996. > > You can immediately launch the quake window with `wt -w _quake`. Or, you should be able to convert an existing window to be the quake window by renaming the window to `_quake` (with the "Rename window" action in the Command Palette). That of course assumes there isn't an already running quake window, of course. > > Does that make sense? Ok, these options are interesting, but that doesn't actually solve the main issue. Why should I right commands or doing renames when I should launch Terminal and Quake window should meet me immediately? (Btw, there should be option in settings to make Quake mode default for launching) And even if I do not check this potential future option and there is default window opened, I should just press Win+` and this window should become Quake, because I checked "make new instance add to existing window" option in settings (if you do not check it, then it should create separate Quake window like it already does now)
claunia commented 2026-01-31 05:37:32 +00:00
Author
Owner
Copy Link

@markusdd commented on GitHub (Apr 20, 2022):

I wish to second that.

We simply need an option to launch in quake mode as default (as there are options for maximized etc.).

Also, quake mode should NOT launch in Focus mode by default, that does not make sense. (at least it should be configurable).

Currently I always need 4 steps to get my windows terminal:

  • launch it from taskbar
  • then launch quake mode
  • close the other window
  • take quake window out of focus mode

This is annoying xD

@markusdd commented on GitHub (Apr 20, 2022): I wish to second that. We simply need an option to launch in quake mode as default (as there are options for maximized etc.). Also, quake mode should NOT launch in Focus mode by default, that does not make sense. (at least it should be configurable). Currently I always need 4 steps to get my windows terminal: - launch it from taskbar - then launch quake mode - close the other window - take quake window out of focus mode This is annoying xD
claunia commented 2026-01-31 05:37:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2022):

Okay yea, between the two of you, it sounds like you're looking for

/dup #9996
/dup #9992

FYI you don't need to use the quakeMode action to summon the window - you could always just rebind win+` to a plain old globalSummon action. Then you'd summon whatever terminal window you were already using, without the focus mode baggage attached. You can even use globalSummon with a dropdownDuration if that's really important (though, you can't currently dock the window to the top of the monitor outside the _quake window).

@zadjii-msft commented on GitHub (Apr 20, 2022): Okay yea, between the two of you, it sounds like you're looking for /dup #9996 /dup #9992 FYI you don't need to use the `quakeMode` action to summon the window - you could always just rebind <kbd>win+\`</kbd> to a plain old [`globalSummon`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-summon) action. Then you'd summon whatever terminal window you were already using, without the focus mode baggage attached. You can even use globalSummon with a dropdownDuration if that's really important (though, you can't currently dock the window to the top of the monitor outside the `_quake` window).
claunia commented 2026-01-31 05:37:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 20, 2022):

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 (Apr 20, 2022): 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!
claunia commented 2026-01-31 05:37:33 +00:00
Author
Owner
Copy Link

@markusdd commented on GitHub (Apr 20, 2022):

Sorry, I do not seem to understand this. I have now put this globalSummon stuff in my JSON settings, still I have to perform the same steps to get my quake window, also the focus mode is still on on first launch.

I just want this terminal to launch in quake mode without focus mode, why is that so difficult? xD

@markusdd commented on GitHub (Apr 20, 2022): Sorry, I do not seem to understand this. I have now put this globalSummon stuff in my JSON settings, still I have to perform the same steps to get my quake window, also the focus mode is still on on first launch. I just want this terminal to launch in quake mode without focus mode, why is that so difficult? xD
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-Windowing Issue-Question Resolution-Answered 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#17274
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?