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

Allow start on login option to launch a hidden quake window #16585

New Issue
Open
opened 2026-01-31 05:16:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:16:29 +00:00
Owner
Copy Link

Originally created by @Kytech on GitHub (Feb 2, 2022).

Description of the new feature/enhancement

Enable Windows Terminal to prepare a hidden quake window on machine startup, preventing the need to first issue the quake mode command from a regular window. Presently, enabling the "launch on machine startup" option only launches a regular window at startup, when it would be nice if the startup behavior prepared a quake window for easy access after startup. Ideally, Windows Terminal should be able to listen to the quake command at machine startup/user login without needing to first start a regular terminal window. Additionally, exiting the shell in the quake terminal (ex via the exit command) requires repeating this process to have a quake terminal available. Ideally, the quake mode command would spawn a new quake window if one doesn't exist.

Proposed technical implementation details (optional)'

Ideally, the Windows Terminal application could be configured so that it's "launch on machine startup" behavior can either A: Launch a regular terminal window as presently implemented, or B: Start a background process that listens to the quake command shortcut, showing the quake window if it already exists, or launching a new one if it does not exist. This process could either be implemented as a service or, probably more ideally, as a user-level background process that creates a tray icon, similar to how PowerToys works to allow it's features to run on startup/login. The system tray icon method is also the same technique that KDE uses for Yakuake on Linux for another project to reference that implements this well.

The use case of this feature, when enabled, would be something like the following: User logs on -> Windows terminal background process/tray process starts on login without showing anything to the screen -> User activates quake command via keyboard -> If quake window currently exists, show it. If not, create the new quake window.

Might be related to #7374, but this feature seems to be a bit larger in scope.

Originally created by @Kytech on GitHub (Feb 2, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> Enable Windows Terminal to prepare a hidden quake window on machine startup, preventing the need to first issue the quake mode command from a regular window. Presently, enabling the "launch on machine startup" option only launches a regular window at startup, when it would be nice if the startup behavior prepared a quake window for easy access after startup. Ideally, Windows Terminal should be able to listen to the quake command at machine startup/user login without needing to first start a regular terminal window. Additionally, exiting the shell in the quake terminal (ex via the `exit` command) requires repeating this process to have a quake terminal available. Ideally, the quake mode command would spawn a new quake window if one doesn't exist. # Proposed technical implementation details (optional)' <!-- A clear and concise description of what you want to happen. --> Ideally, the Windows Terminal application could be configured so that it's "launch on machine startup" behavior can either A: Launch a regular terminal window as presently implemented, or B: Start a background process that listens to the quake command shortcut, showing the quake window if it already exists, or launching a new one if it does not exist. This process could either be implemented as a service or, probably more ideally, as a user-level background process that creates a tray icon, similar to how PowerToys works to allow it's features to run on startup/login. The system tray icon method is also the same technique that KDE uses for Yakuake on Linux for another project to reference that implements this well. The use case of this feature, when enabled, would be something like the following: User logs on -> Windows terminal background process/tray process starts on login without showing anything to the screen -> User activates quake command via keyboard -> If quake window currently exists, show it. If not, create the new quake window. Might be related to #7374, but this feature seems to be a bit larger in scope.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:16:29 +00:00
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 Issue-Feature 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#16585
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?