microsoft / terminal

The new Windows Terminal and the original Windows console host, all in the same place!

MIT License

95.02k stars 8.23k forks source link

Unable to load font X, using font X instead?!? #9360

Closed greggman closed 3 years ago

greggman commented 3 years ago

Environment

Windows build number: Win32NT             10.0.19042.0 Microsoft Windows NT 10.0.19042.0
Windows Terminal version (if applicable): 1.6.10571.0

Steps to reproduce

Run Windows Terminal on my machine (sorry)

Expected behavior

It runs normally

Actual behavior

It displays this nonsense message

WindowsTerminal_BGD4W2SnLW

Was working until I let the Microsoft Store upgrade it 10 minutes ago

DHowett commented 3 years ago

HA! Sorry! That's a really funny bug. If you change the b in your config file (Jetbrains) to B (JetBrains)... does it go away?

@miniksa you may like this one

DHowett commented 3 years ago

What seems to be happening is that we're asking the OS for a font with the wrong case, and it's saying "I couldn't find that. Found this really similar one instead" and we dutifully present that ... "error" ... to the user.

zadjii-msft commented 3 years ago

Maybe we should relax the scenario where we display that error - if we pick one with the same (case-insensitive) name, then maybe just skip the warning.

miniksa commented 3 years ago

I like @zadjii-msft 's idea. Just do an insensitive compare and don't show if it matches.

skyline75489 commented 3 years ago

Sorry is #9157 the same as this? I think that one is also worth noticing.

greggman commented 3 years ago

It was a case issue but ... it worked before the latest update so some change took it from case insensitive to case sensitive.

zadjii-msft commented 3 years ago

The warning was only added in 1.6 (see #8207), so that's what happened there 😉

vibonacci commented 3 years ago

Very funny.

DHowett commented 3 years ago

Yes, that is the central thesis of this bug report. Have you tried the suggested workaround?

miniksa commented 3 years ago

/dup #9375 I will be handling this case in the PR attached to the dupe I'm linking this to.

Thanks

ghost commented 3 years ago

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!