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

Configurable Quake Mode window width, to accommodate ultra-wide resolutions #13903

New Issue
Closed
opened 2026-01-31 03:55:19 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 03:55:19 +00:00
Owner
Copy Link

Originally created by @riverar on GitHub (May 25, 2021).

Summary

Quake Mode (https://github.com/microsoft/terminal/pull/9274) provides, well, a Quake-like console that appears on use of a global hotkey. This console window opens at the maximum width of the active workspace, however, creating usability issues on ultra-wide displays.

Consider a user sitting at the center of this screenshot:
image

Proposal

Allow for a user-configurable width, preferably in relative sizing units (to accommodate resolution changes).

Example:

{
  // ...
  "quakeMode.window.width": "50%"
}
Originally created by @riverar on GitHub (May 25, 2021). # Summary Quake Mode (https://github.com/microsoft/terminal/pull/9274) provides, well, a Quake-like console that appears on use of a global hotkey. This console window opens at the maximum width of the active workspace, however, creating usability issues on ultra-wide displays. Consider a user sitting at the center of this screenshot: ![image](https://user-images.githubusercontent.com/475132/119551409-78fedf00-bd4e-11eb-8fa9-0e41a38c1c61.png) # Proposal Allow for a user-configurable width, preferably in **relative** sizing units (to accommodate resolution changes). Example: ```jsonc { // ... "quakeMode.window.width": "50%" } ```
claunia commented 2026-01-31 03:55:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 25, 2021):

So, IMO quake mode is more of an "easter egg" mode than anything else. If you want exactly the behavior of quake mode, then bind quakeMode. If you want some other behavior, then feel free to bind something else. I personally just use

{ "keys": "win+`", "command": { "action": "globalSummon", "monitor": "any" } },

which just activates the window where it is, without all the other "quake mode" hijinks. So you could bind that, and the window would still obey the normal initialRows, initialCols, etc. Does that seem like a reasonable solution?

(we've also got #9992 tracking "allow users to set settings per-window name", which would let users change the initialPosition, initialRows, etc for the _quake window).

@zadjii-msft commented on GitHub (May 25, 2021): So, IMO quake mode is more of an "easter egg" mode than anything else. If you want _exactly the behavior of quake mode_, then bind `quakeMode`. If you want some other behavior, then feel free to bind something else. I personally just use ```json { "keys": "win+`", "command": { "action": "globalSummon", "monitor": "any" } }, ``` which just activates the window where it is, without all the other "quake mode" hijinks. So you could bind that, and the window would still obey the normal `initialRows`, `initialCols`, etc. Does that seem like a reasonable solution? (we've also got #9992 tracking "allow users to set settings per-window name", which would let users change the `initialPosition`, `initialRows`, etc for the `_quake` window).
claunia commented 2026-01-31 03:55:21 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 25, 2021):

LOL. Yeah, that makes sense.

@zadjii-msft, perhaps we can roll this into "per-window launch properties" where a launch size/initial width for _quake specifies magic?

@DHowett commented on GitHub (May 25, 2021): _LOL_. Yeah, that makes sense. @zadjii-msft, perhaps we can roll this into "per-window launch properties" where a launch size/initial width for `_quake` specifies magic?
claunia commented 2026-01-31 03:55:21 +00:00
Author
Owner
Copy Link

@riverar commented on GitHub (May 25, 2021):

This mode was communicated as such at Build 2021:

Quake Mode allows users to quickly open a new terminal window from anywhere in Windows with a simple keyboard shortcut.

I wasn't aware of the global summon action so I'll try that out. I'll be looking for positioning configuration of that window as well.

If the team consensus is that Quake Mode was designed to be a gimmick and not a useful feature per Build comms, then feel free to close this issue. I'm okay with that.

@riverar commented on GitHub (May 25, 2021): This mode was communicated as such at Build 2021: > Quake Mode allows users to quickly open a new terminal window from anywhere in Windows with a simple keyboard shortcut. I wasn't aware of the global summon action so I'll try that out. I'll be looking for positioning configuration of that window as well. If the team consensus is that _Quake Mode_ was designed to be a gimmick and not a useful feature per Build comms, then feel free to close this issue. I'm okay with that.
claunia commented 2026-01-31 03:55:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 25, 2021):

Meh, yea, that's what we get when we try distilling a big release like this into two sentences 😆

There's actually quite a lot of configuration possible - see the docs for globalSummon

@zadjii-msft commented on GitHub (May 25, 2021): Meh, yea, that's what we get when we try distilling a big release like this into two sentences 😆 There's actually quite a lot of configuration possible - see [the docs for `globalSummon`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-commands)
claunia commented 2026-01-31 03:55:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 25, 2021):

If the team consensus is that Quake Mode was designed to be a gimmick and not a useful feature.

This is not the team's consensus. An "easter egg" that is a specialization of a much more featureful feature is not "a gimmick" that was designed to be "not a useful feature."

Please assume positive intent when you're on this repository. 😄

@DHowett commented on GitHub (May 25, 2021): > If the team consensus is that _Quake Mode_ was designed to be a gimmick and not a useful feature. This is not the team's consensus. An "easter egg" that is a specialization of a much more featureful _feature_ is not "a gimmick" that was designed to be "not a useful feature." Please assume positive intent when you're on this repository. :smile:
claunia commented 2026-01-31 03:55:22 +00:00
Author
Owner
Copy Link

@riverar commented on GitHub (May 25, 2021):

Thanks @DHowett no negative vibes intended. But I completely disagree with your characterization of Quake Mode as an easter egg. It's not communicated that way via official Microsoft comms channels. And "easter egg" implies "no support", hence my comment. Happy to be wrong there.

Regardless, @zadjii-msft's workaround is great, so no changes needed! Closing issue.

@riverar commented on GitHub (May 25, 2021): Thanks @DHowett no negative vibes intended. But I completely disagree with your characterization of Quake Mode as an _easter egg_. It's not communicated that way via official Microsoft comms channels. And "easter egg" implies "no support", hence my comment. Happy to be wrong there. Regardless, @zadjii-msft's workaround is great, so no changes needed! Closing issue.
claunia commented 2026-01-31 03:55:23 +00:00
Author
Owner
Copy Link

@renato-ll commented on GitHub (Aug 3, 2021):

Thanks @DHowett no negative vibes intended. But I completely disagree with your characterization of Quake Mode as an easter egg. It's not communicated that way via official Microsoft comms channels. And "easter egg" implies "no support", hence my comment. Happy to be wrong there.

Regardless, @zadjii-msft's workaround is great, so no changes needed! Closing issue.

Sorry but how did you mannaged to adapt quake mode on ultra wide using the globalSummon directives ? I would like to open the quake mode at the middle of a really big screen with 50% width

@renato-ll commented on GitHub (Aug 3, 2021): > Thanks @DHowett no negative vibes intended. But I completely disagree with your characterization of Quake Mode as an _easter egg_. It's not communicated that way via official Microsoft comms channels. And "easter egg" implies "no support", hence my comment. Happy to be wrong there. > > Regardless, @zadjii-msft's workaround is great, so no changes needed! Closing issue. Sorry but how did you mannaged to adapt quake mode on ultra wide using the globalSummon directives ? I would like to open the quake mode at the middle of a really big screen with 50% width
claunia commented 2026-01-31 03:55:23 +00:00
Author
Owner
Copy Link

@riverar commented on GitHub (Aug 3, 2021):

@xinxilas I didn't. Wasn't worth the trouble.

@riverar commented on GitHub (Aug 3, 2021): @xinxilas I didn't. Wasn't worth the trouble.
claunia commented 2026-01-31 03:55:23 +00:00
Author
Owner
Copy Link

@renato-ll commented on GitHub (Aug 3, 2021):

Lol, ill try to use some custom globalsummon with without quake mode then 😂

@renato-ll commented on GitHub (Aug 3, 2021): Lol, ill try to use some custom globalsummon with without quake mode then 😂
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 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#13903
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?