Conversation
|
Well but we don't ship any fonts. |
|
Be aware that there's no reliable way to ref: nim-lang/Nim#25701 Using appDir is very convenient but is generally discouraged as it usually implies getting elevated permissions. It's ok as a fallback, but you always better start with envs: APPDATA/LOCALAPPDATA (which is idiomatic but difficult to appreciate), then PROGRAMDATA (from Vista), then/or something like |
|
I use getAppDir successfully for about 15 years and symlinks are largely unused on Windows... |
|
What can I say, you miss a lot. Also, it's better not conflate personal experience with statistical significance. Even if it was insignificant, shouldn't we strive to be correct? |
|
No, we should strive to make OSes simpler by removing anti-features from them. And we do that in a first step by pretending the anti-features don't exist. The alternative is that every API documents its signal-safety behavior and apparently the whole world decided, rightly so, that that would be stupid. |
|
You should set up a twitter account, you'll have a blast with the hot takes. "anti-features" = "features I don't need", cool. |
Even if the DejaVuSansMono.ttf font is installed on Windows, it is sometimes not found by name in the system folder. I have implemented a more portable approach: the application now looks for fonts in the executable's directory before falling back to the default system logic. This ensures the app works correctly even if system font detection fails.