-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Not recognized as monospace by fontconfig #840
Comments
I'm having the same issue and am working around it by overwriting the spacing in fontconfig: Create the file
Then update the font-cache:
|
Thanks! Added to https://github.com/tonsky/FiraCode/wiki/Troubleshooting |
@ksonj Your solution is not working for me. I have tried this with "Noto Sans Mono" which has advance widths of (0, 600, 1200, 1800) afaik, which provides no spacing value at all. Using your config example, fc-match will return the font and show spacing of 100, but fc-list does not pick up on it, even after fc-cache. Any ideas why that might be? Would you be able to confirm if you can do the same for "Noto Sans Mono" so that I can know if it's something with my system or font specific? |
The font is not recognized as monospace by some applications (see my initial ticket for the kitty terminal kovidgoyal/kitty#1968)
I believe the problem is that fontconfig reports the font as having
spacing: 90(i)(s)
I ran
git bisect
and found this to be the case since commit b32369cfont: FiraCode-Regular v2 otf
os: Arch Linux 5.2.14-arch2-1-ARCH
installed from arch repo community/otf-fira-code
My
fc-list
output:The text was updated successfully, but these errors were encountered: