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

Force Quake mode window to a certain monitor (Multi-Monitor setup) #14593

New Issue
Closed
opened 2026-01-31 04:14:25 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 04:14:25 +00:00
Owner
Copy Link

Originally created by @hensz on GitHub (Jul 20, 2021).

Hi there!

Currently on my setup (I'm using two screens with the same screen resolution) when I hide the Quake mode window and summon it again, it's displayed on the screen of the currently active window. For my workflow it would be better if the window would appear at the same position where I hid it before.

Is this already possible, if yes, with which setting? If not, then it would be great to have such a feature/setting.

Thanks!
Torsten

Originally created by @hensz on GitHub (Jul 20, 2021). Hi there! Currently on my setup (I'm using two screens with the same screen resolution) when I hide the Quake mode window and summon it again, it's displayed on the screen of the currently active window. For my workflow it would be better if the window would appear at the same position where I hid it before. Is this already possible, if yes, with which setting? If not, then it would be great to have such a feature/setting. Thanks! Torsten
claunia commented 2026-01-31 04:14:27 +00:00
Author
Owner
Copy Link

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

So the "quake mode" window is just a special type of window, with a specialization of the globalSummon action. It's not all that configurable by itself. The quakeMode action will always summon the window named _quake, and will always open on the monitor where the mouse is.

What you can do, though, is rebind win+` to a different globalSummon action. The following will be equivalent to the quakeMode action, but without the requirement that the window's name is _quake:

{ "keys": "win+`", "command": { "action": "globalSummon", "dropdownDuration": 200, "toggleVisibility": true, "monitor": "any", "desktop": "toCurrent" } }

Granted, that won't have the same "snap to the top" behavior, nor will it do the "minimize to tray" thing that _quake does in 1.10, but we're tracking improvements to allow other windows to do those things in #8888 and #9992.

@zadjii-msft commented on GitHub (Jul 20, 2021): So the "quake mode" window is just a special type of window, with a specialization of the `globalSummon` action. It's not all that configurable by itself. The `quakeMode` action will always summon the window named `_quake`, and will always open on the monitor where the mouse is. What you _can_ do, though, is rebind <kbd>win+\`</kbd> to a different `globalSummon` action. The following will be equivalent to the `quakeMode` action, but without the requirement that the window's name is `_quake`: ```json { "keys": "win+`", "command": { "action": "globalSummon", "dropdownDuration": 200, "toggleVisibility": true, "monitor": "any", "desktop": "toCurrent" } } ``` Granted, that won't have the same "snap to the top" behavior, nor will it do the "minimize to tray" thing that `_quake` does in 1.10, but we're tracking improvements to allow other windows to do those things in #8888 and #9992.
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 Issue-Question Needs-Tag-Fix Needs-Triage Product-Terminal Resolution-Answered
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#14593
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?