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

Windows Terminal Quake Mode does not adjust width after changing screen resolution #22338

New Issue
Closed
opened 2026-01-31 08:10:12 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:10:12 +00:00
Owner
Copy Link

Originally created by @CherryDT on GitHub (Oct 2, 2024).

Windows Terminal version

1.22.2702.0

Windows build number

10.0.19045.4894

Other Software

No response

Steps to reproduce

Open quake mode
Switch screen resolution to a larger screen or connect external monitor with larger resolution or disconnect external monitor with smaller resolution you had it running on
Show terminal again

Expected Behavior

Quake mode should always extend to the full width of the screen. At least hiding and showing the quake mode window again should make it adjust itself to fit the width again.

Actual Behavior

Quake mode window no longer extends to the full width of the screen, it is stuck at a smaller width.

20241002-055218-LuwTBdRvNN

Here you can see how it looks after I connected my 5120x1440 screen. My laptop screen resolution was 1920x1080 and now the terminal is stuck at a width of 1920 instead of filling the full 5120 pixels

Even pressing Alt+Enter twice does not fix it, it will then go back to the broken size from before. The only way I found to fix it (other than restarting) is to focus a different monitor, open quake mode there, then go back to the other monitor and reopen it there. But unfortunately this doesn't work in the case in which I had an external monitor with smaller resolution than my laptop screen, disconnected that monitor and now got a bad width on my laptop screen as in this scenario there is no second monitor anymore to fix it...

Originally created by @CherryDT on GitHub (Oct 2, 2024). ### Windows Terminal version 1.22.2702.0 ### Windows build number 10.0.19045.4894 ### Other Software _No response_ ### Steps to reproduce Open quake mode Switch screen resolution to a larger screen or connect external monitor with larger resolution or disconnect external monitor with smaller resolution you had it running on Show terminal again ### Expected Behavior Quake mode should always extend to the full width of the screen. At least hiding and showing the quake mode window again should make it adjust itself to fit the width again. ### Actual Behavior Quake mode window no longer extends to the full width of the screen, it is stuck at a smaller width. ![20241002-055218-LuwTBdRvNN](https://github.com/user-attachments/assets/501a49fb-bdd5-4c8f-aee0-7b795b8b53c9) Here you can see how it looks after I connected my 5120x1440 screen. My laptop screen resolution was 1920x1080 and now the terminal is stuck at a width of 1920 instead of filling the full 5120 pixels Even pressing Alt+Enter twice does not fix it, it will then go back to the broken size from before. The only way I found to fix it (other than restarting) is to focus a different monitor, open quake mode there, then go back to the other monitor and reopen it there. But unfortunately this doesn't work in the case in which I had an external monitor with smaller resolution than my laptop screen, disconnected that monitor and now got a bad width on my laptop screen as in this scenario there is no second monitor anymore to fix it...
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:10:12 +00:00
claunia commented 2026-01-31 08:10:13 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Oct 2, 2024):

We've found some similar issues:

  • #11125 , similarity score: 90%
  • #16175 , similarity score: 84%
  • #10199 , similarity score: 84%
  • #12785 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Oct 2, 2024): We've found some similar issues: - #11125 , similarity score: 90% - #16175 , similarity score: 84% - #10199 , similarity score: 84% - #12785 , similarity score: 83% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
claunia commented 2026-01-31 08:10:13 +00:00
Author
Owner
Copy Link

@CherryDT commented on GitHub (Oct 2, 2024):

Right... duplicate of #11125

Also, as workaround I now run this AutoHotkey (v1) script whenever it's messed up:

WinGet, windowID, ID, ahk_class CASCADIA_HOSTING_WINDOW_CLASS

if windowID
{
    WinGetPos, x, y, width, height, ahk_id %windowID%
    SysGet, monitor, Monitor, %x%, %y%
    SysGet, MonitorWorkArea, MonitorWorkArea, %monitor%
    screenWidth := MonitorWorkAreaRight - MonitorWorkAreaLeft
    screenHeight := MonitorWorkAreaBottom - MonitorWorkAreaTop

    tolerance := 10
    if (x >= MonitorWorkAreaLeft - tolerance and x <= MonitorWorkAreaLeft + tolerance and y >= MonitorWorkAreaTop - tolerance and y <= MonitorWorkAreaTop + tolerance)
    {
        offsetX := x - MonitorWorkAreaLeft
        offsetY := y - MonitorWorkAreaTop

        adjustedWidth := screenWidth - (2 * offsetX)
        adjustedHeight := (screenHeight / 2) - (2 * offsetY)

        WinMove, ahk_id %windowID%, , %x%, %y%, %adjustedWidth%, %adjustedHeight%
    }
}
@CherryDT commented on GitHub (Oct 2, 2024): Right... duplicate of #11125 --- Also, as workaround I now run this AutoHotkey (v1) script whenever it's messed up: ``` WinGet, windowID, ID, ahk_class CASCADIA_HOSTING_WINDOW_CLASS if windowID { WinGetPos, x, y, width, height, ahk_id %windowID% SysGet, monitor, Monitor, %x%, %y% SysGet, MonitorWorkArea, MonitorWorkArea, %monitor% screenWidth := MonitorWorkAreaRight - MonitorWorkAreaLeft screenHeight := MonitorWorkAreaBottom - MonitorWorkAreaTop tolerance := 10 if (x >= MonitorWorkAreaLeft - tolerance and x <= MonitorWorkAreaLeft + tolerance and y >= MonitorWorkAreaTop - tolerance and y <= MonitorWorkAreaTop + tolerance) { offsetX := x - MonitorWorkAreaLeft offsetY := y - MonitorWorkAreaTop adjustedWidth := screenWidth - (2 * offsetX) adjustedHeight := (screenHeight / 2) - (2 * offsetY) WinMove, ahk_id %windowID%, , %x%, %y%, %adjustedWidth%, %adjustedHeight% } } ```
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-Bug Needs-Triage
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#22338
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?