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

Always-on-top quake mode window #14167

New Issue
Open
opened 2026-01-31 04:02:50 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:02:50 +00:00
Owner
Copy Link

Originally created by @cerebrate on GitHub (Jun 9, 2021).

Description of the new feature/enhancement

The way I use the _quake window (for a one-off command or series of commands), it usually has my attention for as long as it's up, but on the occasions where I turn away to do other things, it can easily get lost in the mess and/or confused with one of my regular terminal windows. Having it always-on-top such that it is either dropped-down on-top or not makes this less likely to happen in my workflow.

Proposed technical implementation details (optional)

While just making the _quake window always-on-top by default would fit the letter of the request, I'd much rather have always-on-topness added as a parameter that can be used with quakeMode and globalSummon to influence the parameters of windows they create. It would also be useful to have it as a command-line option for use with -w -- I currently use a _C:\Users\avatar\AppData\Local\Microsoft\WindowsApps\wt.exe -w _quake to automatically open the _quake window when I log on, and while I can toggle on always-on-topness after opening it, I would prefer to be able to have that in the shortcut.

Originally created by @cerebrate on GitHub (Jun 9, 2021). # Description of the new feature/enhancement The way I use the _quake window (for a one-off command or series of commands), it usually has my attention for as long as it's up, but on the occasions where I turn away to do other things, it can easily get lost in the mess and/or confused with one of my regular terminal windows. Having it always-on-top such that it is either dropped-down on-top or not makes this less likely to happen in my workflow. # Proposed technical implementation details (optional) While just making the _quake window always-on-top by default would fit the letter of the request, I'd much rather have always-on-topness added as a parameter that can be used with _quakeMode_ and _globalSummon_ to influence the parameters of windows they create. It would also be useful to have it as a command-line option for use with _-w_ -- I currently use a `_C:\Users\avatar\AppData\Local\Microsoft\WindowsApps\wt.exe -w _quake` to automatically open the _quake window when I log on, and while I can toggle on always-on-topness after opening it, I would prefer to be able to have that in the shortcut.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:02:50 +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#14167
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?