Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some characters are not rendered at small font sizes #11376

Closed
boltronics opened this issue Sep 30, 2021 · 5 comments
Closed

Some characters are not rendered at small font sizes #11376

boltronics opened this issue Sep 30, 2021 · 5 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@boltronics
Copy link

Windows Terminal version (or Windows build number)

1.10.2383.0

Other Software

tree v1.8.0 (inside a Debian WSL2 environment)

Steps to reproduce

Set the Font size to 8, and Font face to something like Consolas, or Liberation Mono.

Alternatively, set Font size to 9 and set Font face to Terminus (TTF) For Windows (my personal preference).

Run tree

(or run pass or any other software that relies on it).

Expected Behavior

You should see something like:

~$ tree dir
dir/
├── file1.txt
└── file2.txt

Actual Behavior

Instead, you'll see something like:

~$ tree dir
dir/
    file1.txt
    file2.txt

It took me a lot of testing to figure out that I needed to bump my font size up for these characters to render, since every font I tried wouldn't show it (although that was apparently just luck since some fonts do render the lines with varying degrees of success). I initially thought the colour was somehow matching the background, since the characters were present since I could copy them. Unfortunately, I find that increasing the font size to the required degree is not acceptable.

A more acceptable work-around is to define a shell function like so:

~$ tree() { TREE_CHARSET='C' /usr/bin/tree "${@}" ; }
~$ tree testdir/
testdir/
|-- file1.txt
`-- file2.txt

0 directories, 1 file
~$

Of course it still looks more ugly than it should, but at least it shows something without affecting everything else.

If I apt install terminator and the Terminus fonts and run it under VcXsrv, it works perfectly.

image
(Windows Terminal on the left, Terminator on the right)

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 30, 2021
@elsaco
Copy link

elsaco commented Sep 30, 2021

@boltronics "tree -A" turns on ANSI line graphics hack. Works every time!

@boltronics
Copy link
Author

@elsaco Thanks for the suggestion. Unfortunately that made no difference for me.
image
Also, when pressing Ctrl+C because I accidentally ran tree -A across a large directory, I got the corruption you see in the top pane. I've never seen that happen before (although that'll be unrelated).

@boltronics
Copy link
Author

FWIW, corruption was fixed with echo ^N (that's ctrl+v, ctrl+n) although I could have just reopened a new window I guess.

@j4james
Copy link
Collaborator

j4james commented Sep 30, 2021

I think this is probably covered by #7927 or #5897 (see for example #5897 (comment)). Possibly also #6161.

@boltronics
Copy link
Author

Thanks @j4james you are right, it's a dupe of #7927 I'd say. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

3 participants