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

Snapping window to left side of right screen loses part of first character column #4932

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

Originally created by @patridge on GitHub (Nov 11, 2019).

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Display setup:
Left: Surface Book 1, 3000x2000 @ 200%
Right: Ultrawide, 3440x1440 @ 100%

Steps to reproduce

  1. Launch Terminal, move to right display
  2. Maximize on right display with Win+Up
  3. Set to left half of right display with Win+Left

Expected behavior

The Terminal window should be completely contained within the left half of the right display.

Actual behavior

The Terminal window will have the left-most chrome border and some of the console output on the left screen.

A screenshot of this is tough, but notice that the border is overlapping the adjacent scroll bar that is maximized on the left display here.

Screenshot of overlap between a Terminal window set to use the left half of a right-hand display and the window adjacent to the left that is maximized to take up the full left display

Workaround hack

Once the window is consuming half the screen, you can send it to the other displays left half with Win+Shift+Left/+Right. Then, sending it back to the original, right display with Win+Shift+Left/+Right will cause it to fit where expected.

Here is that same section of adjacent windows after the workaround, showing no overlap on the scrollbar.

Screenshot showing no overlap between Terminal and left-adjacent window after following workaround steps

Originally created by @patridge on GitHub (Nov 11, 2019). # Environment ```none Windows build number: 10.0.18362.0 Windows Terminal version (if applicable): 0.6.2951.0 Display setup: Left: Surface Book 1, 3000x2000 @ 200% Right: Ultrawide, 3440x1440 @ 100% ``` # Steps to reproduce 1. Launch Terminal, move to right display 1. Maximize on right display with Win+Up 1. Set to left half of right display with Win+Left # Expected behavior The Terminal window should be completely contained within the left half of the right display. # Actual behavior The Terminal window will have the left-most chrome border and some of the console output on the left screen. A screenshot of this is tough, but notice that the border is overlapping the adjacent scroll bar that is maximized on the left display here. ![Screenshot of overlap between a Terminal window set to use the left half of a right-hand display and the window adjacent to the left that is maximized to take up the full left display](https://user-images.githubusercontent.com/713665/68619303-78626880-0488-11ea-93d0-433818562cfc.png) ## Workaround hack Once the window is consuming half the screen, you can send it to the other displays left half with Win+Shift+Left/+Right. Then, sending it back to the original, right display with Win+Shift+Left/+Right will cause it to fit where expected. Here is that same section of adjacent windows after the workaround, showing no overlap on the scrollbar. ![Screenshot showing no overlap between Terminal and left-adjacent window after following workaround steps](https://user-images.githubusercontent.com/713665/68619424-b3649c00-0488-11ea-929a-5d36608b0a73.png)
claunia added the Resolution-Duplicate label 2026-01-31 00:01:01 +00:00
claunia commented 2026-01-31 00:01:03 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Nov 11, 2019):

This looks like a /dupe of #3394. A bunch of stuff related to the border and the pixel counts around the edge was fixed there. If this still happens against master or against v0.7 when it comes out, please reactivate then.

@miniksa commented on GitHub (Nov 11, 2019): This looks like a /dupe of #3394. A bunch of stuff related to the border and the pixel counts around the edge was fixed there. If this still happens against `master` or against v0.7 when it comes out, please reactivate then.
claunia commented 2026-01-31 00:01:03 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 11, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 11, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 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#4932
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?