Troubleshooting
See Installing
Easiest way is to compare the shape of @ & and r with the reference image:
Consult this wiki (see above ↑) for instruction on how to do that.
Issues: #291
Consult CHANGELOG to see when it was last updated.
Some Unicode characters are not in Fira Code. You can start by checking Fira Mono doc and Fira Code Changelog.
If character is missing, you’ll see glyphs from a fallback font chosen by your system, which might have drastically different look and metrics. Create an issue and I’ll try to add it to the Fira Code in the next version.
Issues: #812, #811, #800, #796
Make sure you installed TTF, not OTF files. Issues: #798
Known problem, can’t be easily fixed.
-
Uneven spacing in
===and!==at certain font sizes, esp. on Windows #405 #243 #119 #114. The issue with===could be worked around by increasing/decreasing the font size by 0.5, so go from 12 to 12.5 or from 13.5 to 13.0 and test.
Unfortunately this can’t be fixed for all terminals because they have different ways of calculate font metrics. See this comment
This is an issue with your editor and how it handles tokenization/syntax highlighting. Nothing can be done in a font to work around that. Report your problem to the corresponding editor’s issue tracker.
-
All ligatures with dashes in Visual Studio (not Code) #422 #395 #360 #273 #259 #233 #220 #196 #181 #157 #99 #43 #32
-
Atom/VS Code are known to break certain ligatures in certain syntaxes #361 #353 #348 #328 #326 #235
Go to C:\Windows\Fonts with cmd.exe, find and delete everything having Fira in the file name. It’s important that you use terminal commands, not Explorer.
Issues: #589 #581 #398 IDEA-159901
Fira Code does not have italics at all. If you see italicized glyphs it means your editor is “faking” them.
Issues: #840