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

Large spacing between characters and bottom border in focus mode #17131

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

Originally created by @Noicdi on GitHub (Apr 1, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19044.0

Other Software

Windows terminal in focus mode

OS: Arch Linux on Windows 10 x86_64
Kernel: 5.10.102.1-microsoft-standard-WSL2

vim 8.2
tmux
ranger 1.9.3

Steps to reproduce

Set the startup mode to focus mode and compare the focus mode with the default mode

Expected Behavior

This doesn't interfere with use, but it is very hard for OCD sufferers. I wish the focus mode had the same interval size as the default mode

Actual Behavior

When opening some programs in focus mode, the bottom border of the terminal has a larger distance from the characters

Take tmux status bar as an example, you can see that the status bar has a larger distance from the bottom border (the distance between the status bar and the left and right borders is normal); in default mode, it is normal
1

Similarly, take vim and ranger for example, this problem exists, but it is normal in default mode
4
2-false

I had changed the size of the window border spacing, but it didn't work. Still using tmux as an example, in focus mode, changing the value of the window border spacing changes the distance between the status bar and the left and right borders, but there is still a large distance between the status bar and the lower border
5
6

Originally created by @Noicdi on GitHub (Apr 1, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19044.0 ### Other Software Windows terminal in focus mode OS: Arch Linux on Windows 10 x86_64 Kernel: 5.10.102.1-microsoft-standard-WSL2 vim 8.2 tmux ranger 1.9.3 ### Steps to reproduce Set the startup mode to focus mode and compare the focus mode with the default mode ### Expected Behavior This doesn't interfere with use, but it is very hard for OCD sufferers. I wish the focus mode had the same interval size as the default mode ### Actual Behavior When opening some programs in focus mode, the bottom border of the terminal has a larger distance from the characters Take tmux status bar as an example, you can see that the status bar has a larger distance from the bottom border (the distance between the status bar and the left and right borders is normal); in default mode, it is normal ![1](https://user-images.githubusercontent.com/56010105/161204519-e57ac093-56a3-40af-a0a2-3eb94b5d9a06.png) Similarly, take vim and ranger for example, this problem exists, but it is normal in default mode ![4](https://user-images.githubusercontent.com/56010105/161204595-2df2fef9-a48a-49ef-a211-329bd7a5ea06.png) ![2-false](https://user-images.githubusercontent.com/56010105/161204619-231f726a-f1ae-4817-83ae-abe3da812c78.png) I had changed the size of the window border spacing, but it didn't work. Still using tmux as an example, in focus mode, changing the value of the window border spacing changes the distance between the status bar and the left and right borders, but there is still a large distance between the status bar and the lower border ![5](https://user-images.githubusercontent.com/56010105/161205402-4d124682-cc18-40e2-9b05-5b774a95eee7.png) ![6](https://user-images.githubusercontent.com/56010105/161205419-76a40fdf-ca26-4426-a7ba-34d9a97b845c.png)
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:33:02 +00:00
claunia commented 2026-01-31 05:33:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 24, 2022):

This looks like a riff on #13155, but with focus mode instead. I suppose focus mode doesn't cause the window to snap to the character boundaries immediately, so entering it would cause the gutters to appear.

@zadjii-msft commented on GitHub (May 24, 2022): This looks like a riff on #13155, but with focus mode instead. I suppose focus mode doesn't cause the window to snap to the character boundaries immediately, so entering it would cause the gutters to appear.
claunia commented 2026-01-31 05:33:04 +00:00
Author
Owner
Copy Link

@Noicdi commented on GitHub (May 25, 2022):

This looks like a riff on #13155, but with focus mode instead. I suppose focus mode doesn't cause the window to snap to the character boundaries immediately, so entering it would cause the gutters to appear.

I do not know much about this, but recently in the use of the process, this problem has rarely appeared

Thank you!

@Noicdi commented on GitHub (May 25, 2022): > This looks like a riff on #13155, but with focus mode instead. I suppose focus mode doesn't cause the window to snap to the character boundaries immediately, so entering it would cause the gutters to appear. I do not know much about this, but recently in the use of the process, this problem has rarely appeared Thank you!
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-Tag-Fix 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#17131
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?