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

Windows Terminal does not find font on start #12079

Closed
Alexciao opened this issue Jan 3, 2022 · 5 comments
Closed

Windows Terminal does not find font on start #12079

Alexciao opened this issue Jan 3, 2022 · 5 comments
Labels
Area-Fonts Related to the font Area-Settings Issues related to settings and customizability, for console or terminal Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Alexciao
Copy link

Alexciao commented Jan 3, 2022

Windows Terminal version

1.11.3471.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

Open Windows Terminal.

Expected Behavior

The expected behavior is that WT would load just fine without any errors.

Actual Behavior

WT loads and shows a "Can't find font" error.
image

This can be fixed by going to Settings and hitting "Save" without modifying anything, but it is rather annoying, especially because I use a custom prompt that makes use of a "Nerd Font", and displays incorrectly without that.

@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 Jan 3, 2022
@237dmitry
Copy link

Maybe wrong font face? Try Nerd Font instead of NF

@zadjii-msft
Copy link
Member

Oh interesting. This isn't #11648 then. If you're trying to use the nerd fonts version, the Terminal probably should be able to load this without any issues. What string did you enter in the settings file to set the font to CaskaydiaCove NF?

Curious that the initial load gets it wrong, but then apparently the subsequent load of the SUI falls back to the font you expected. We probably need to align those two code paths.

@zadjii-msft zadjii-msft added Area-Fonts Related to the font Area-Settings Issues related to settings and customizability, for console or terminal Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. labels Jan 3, 2022
@zadjii-msft
Copy link
Member

After looking through the backlog, I found #11583 which looks like the same thing, so I'm gonna merge these threads. /dup #11583

Thanks!

@ghost
Copy link

ghost commented Jan 4, 2022

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 ghost closed this as completed Jan 4, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jan 4, 2022
@Alexciao
Copy link
Author

Alexciao commented Jan 4, 2022

Oh interesting. This isn't #11648 then. If you're trying to use the nerd fonts version, the Terminal probably should be able to load this without any issues. What string did you enter in the settings file to set the font to CaskaydiaCove NF?

I just changed it via settings UI.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Fonts Related to the font Area-Settings Issues related to settings and customizability, for console or terminal Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants