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

Normalize terminal padding in maximized or fullscreened windows #9011

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

Originally created by @dkter on GitHub (Jun 13, 2020).

Description of the new feature/enhancement

When the window is in an un-maximized state, Terminal snaps window resizes to the closest character, which makes sense -- this way, the terminal padding on all 4 edges is what it's set to in settings.json.
However, when the window is maximized or in fullscreen, Terminal's size depends on the size of the monitor, which means the padding is often mismatched. When this happens, Terminal preserves the top and left padding. This makes some graphical CLI programs look a bit odd:

A full-screened Terminal with weechat running with equal padding on the left and top sides, but greater than usual padding on the right and especially the bottom

It might be nice to have an option to make the left-right and top-bottom paddings equal in this situation, so that the terminal content is centred within the window rather than at the top left.

Proposed technical implementation details (optional)

Of course, the padding setting should still be used as a minimum padding, and I think it makes sense to have this as a per-profile option (it makes more sense when you're running full-screen CLI programs like weechat, than if you're just running a shell.)

Originally created by @dkter on GitHub (Jun 13, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement When the window is in an un-maximized state, Terminal snaps window resizes to the closest character, which makes sense -- this way, the terminal padding on all 4 edges is what it's set to in `settings.json`. However, when the window is maximized or in fullscreen, Terminal's size depends on the size of the monitor, which means the padding is often mismatched. When this happens, Terminal preserves the top and left padding. This makes some graphical CLI programs look a bit odd: ![A full-screened Terminal with weechat running with equal padding on the left and top sides, but greater than usual padding on the right and especially the bottom](https://user-images.githubusercontent.com/34610081/84579691-fe87ba00-ad9d-11ea-8fb6-d3d422d6a0cc.png) It might be nice to have an option to make the left-right and top-bottom paddings equal in this situation, so that the terminal content is centred within the window rather than at the top left. # Proposed technical implementation details (optional) Of course, the `padding` setting should still be used as a minimum padding, and I think it makes sense to have this as a per-profile option (it makes more sense when you're running full-screen CLI programs like `weechat`, than if you're just running a shell.)
claunia added the Help WantedIssue-TaskProduct-TerminalArea-TerminalControl labels 2026-01-31 01:43:44 +00:00
claunia commented 2026-01-31 01:43:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 15, 2020):

I really don't hate this idea actually. I'd probably make it an opt in setting, but it shouldn't be too hard to figure out when the Terminal is entering the "maximized" state, and adjust the padding accordingly.

@zadjii-msft commented on GitHub (Jun 15, 2020): I really don't hate this idea actually. I'd probably make it an opt in setting, but it shouldn't be too hard to figure out when the Terminal is entering the "maximized" state, and adjust the padding accordingly.
claunia commented 2026-01-31 01:43:46 +00:00
Author
Owner
Copy Link

@beviu commented on GitHub (Jun 22, 2020):

Even if we make the padding around the SwapChainPanel uniform, there is still the scroll bar at the right which adds "empty space" when it automatically shrinks to the little gray bar like in the screenshot, because it still takes the same space as before it shrank.

@beviu commented on GitHub (Jun 22, 2020): Even if we make the padding around the `SwapChainPanel` uniform, there is still the scroll bar at the right which adds "empty space" when it automatically shrinks to the little gray bar like in the screenshot, because it still takes the same space as before it shrank.
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 Area-TerminalControl Help Wanted Issue-Task 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#9011
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?