DPI Setting will break the characters should be connected #7408

Closed
opened 2026-01-31 01:03:16 +00:00 by claunia · 2 comments
Owner

Originally created by @kix99aug on GitHub (Apr 14, 2020).

Environment

Windows build number: 
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):

0.10.781.0

Any other software?

With oh-my-posh plugin

Steps to reproduce

If set the system DPI to 100%, the character will display in the right way.
But set the system DPI to 125%. there will be a wired line between the characters.

Expected behavior

image

Actual behavior

image

Originally created by @kix99aug on GitHub (Apr 14, 2020). # Environment ```none Windows build number: Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): 0.10.781.0 Any other software? With oh-my-posh plugin ``` # Steps to reproduce If set the system DPI to 100%, the character will display in the right way. But set the system DPI to 125%. there will be a wired line between the characters. <!-- A description of how to trigger this bug. --> # Expected behavior ![image](https://user-images.githubusercontent.com/10905628/79246179-afabca00-7eab-11ea-8247-b85399d53521.png) # Actual behavior ![image](https://user-images.githubusercontent.com/10905628/79246115-9efb5400-7eab-11ea-9230-7f1399ff1e71.png)
claunia added the Resolution-Duplicate label 2026-01-31 01:03:16 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Apr 14, 2020):

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #3626 for more discussion.

/dup #3626

This was also actually resolved in #5149, and should be fixed in the 0.11 release of the Terminal (coming soonTM)

@zadjii-msft commented on GitHub (Apr 14, 2020): Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #3626 for more discussion. /dup #3626 This was also actually resolved in #5149, and should be fixed in the 0.11 release of the Terminal (coming soon<sup>TM</sup>)
Author
Owner

@ghost commented on GitHub (Apr 14, 2020):

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 (Apr 14, 2020): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7408