tonsky/FiraCode
1
1
Fork 0
mirror of https://github.com/tonsky/FiraCode.git synced 2024-10-04 00:31:49 +03:00
Code Issues Projects Releases Wiki Activity

Updated Troubleshooting (markdown)

Nikita Prokopov 2019-09-16 16:11:11 +02:00
parent 9c8c6a4426
commit 4e942fb20a
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Troubleshooting.md

@ -1,8 +1,8 @@
# Make sure you actually installed Fira Code ## Make sure you actually installed Fira Code
See https://github.com/tonsky/FiraCode/wiki See https://github.com/tonsky/FiraCode/wiki
# Make sure the font your editor displays is actually Fira Code ## Make sure the font your editor displays is actually Fira Code
Easiest way is to compare the shape of `@` `&` and `r` with the reference image: Easiest way is to compare the shape of `@` `&` and `r` with the reference image:
@ -10,17 +10,17 @@ Easiest way is to compare the shape of `@` `&` and `r` with the reference image:
Issues: [#393](https://github.com/tonsky/FiraCode/issues/393) [#373](https://github.com/tonsky/FiraCode/issues/373) [#227](https://github.com/tonsky/FiraCode/issues/227) Issues: [#393](https://github.com/tonsky/FiraCode/issues/393) [#373](https://github.com/tonsky/FiraCode/issues/373) [#227](https://github.com/tonsky/FiraCode/issues/227)
# Make sure you’ve enabled ligatures in your editor ## Make sure you’ve enabled ligatures in your editor
Consult this wiki (see above ↑) for instruction on how to do that. Consult this wiki (see above ↑) for instruction on how to do that.
Issues: [#291](https://github.com/tonsky/FiraCode/issues/291) Issues: [#291](https://github.com/tonsky/FiraCode/issues/291)
# Make sure you’re on the latest version of Fira Code ## Make sure you’re on the latest version of Fira Code
Consult [CHANGELOG](https://github.com/tonsky/FiraCode/blob/master/CHANGELOG.md) to see when it was last updated. Consult [CHANGELOG](https://github.com/tonsky/FiraCode/blob/master/CHANGELOG.md) to see when it was last updated.
# Characters look weird, not monospaced, not rendered at all ## Characters look weird, not monospaced, not rendered at all
Some Unicode characters are not in Fira Code. You can start by checking [Fira Mono doc](https://github.com/bBoxType/FiraSans/raw/master/Fira_Mono_3_2/PDF/FiraMono-Regular.otf.pdf) and [Fira Code Changelog](https://github.com/tonsky/FiraCode/blob/master/CHANGELOG.md). Some Unicode characters are not in Fira Code. You can start by checking [Fira Mono doc](https://github.com/bBoxType/FiraSans/raw/master/Fira_Mono_3_2/PDF/FiraMono-Regular.otf.pdf) and [Fira Code Changelog](https://github.com/tonsky/FiraCode/blob/master/CHANGELOG.md).
@ -28,7 +28,7 @@ If character is missing, you’ll see glyphs from a fallback font chosen by your
Issues: [#812](https://github.com/tonsky/FiraCode/issues/812), [#811](https://github.com/tonsky/FiraCode/issues/811), [#800](https://github.com/tonsky/FiraCode/issues/800), [#796](https://github.com/tonsky/FiraCode/issues/796) Issues: [#812](https://github.com/tonsky/FiraCode/issues/812), [#811](https://github.com/tonsky/FiraCode/issues/811), [#800](https://github.com/tonsky/FiraCode/issues/800), [#796](https://github.com/tonsky/FiraCode/issues/796)
# Hinting issues ## Hinting issues
Known problem, can’t be easily fixed. Known problem, can’t be easily fixed.
@ -36,13 +36,13 @@ Known problem, can’t be easily fixed.
* Different height of `[]` at certain font sizes [#332](https://github.com/tonsky/FiraCode/issues/332) [#251](https://github.com/tonsky/FiraCode/issues/251) * Different height of `[]` at certain font sizes [#332](https://github.com/tonsky/FiraCode/issues/332) [#251](https://github.com/tonsky/FiraCode/issues/251)
# Powerline characters are of slightly wrong size ## Powerline characters are of slightly wrong size
Unfortunately this can’t be fixed for all terminals because they have different ways of calculate font metrics. See [this comment](https://github.com/tonsky/FiraCode/issues/44#issuecomment-187305276) Unfortunately this can’t be fixed for all terminals because they have different ways of calculate font metrics. See [this comment](https://github.com/tonsky/FiraCode/issues/44#issuecomment-187305276)
Issues: [#426](https://github.com/tonsky/FiraCode/issues/426) [#131](https://github.com/tonsky/FiraCode/issues/131) [#44](https://github.com/tonsky/FiraCode/issues/44) Issues: [#426](https://github.com/tonsky/FiraCode/issues/426) [#131](https://github.com/tonsky/FiraCode/issues/131) [#44](https://github.com/tonsky/FiraCode/issues/44)
# Some ligatures work while some don’t ## Some ligatures work while some don’t
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. 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.
@ -52,18 +52,18 @@ This is an issue with your editor and how it handles tokenization/syntax highlig
- Atom/VS Code are known to break certain ligatures in certain syntaxes [#361](https://github.com/tonsky/FiraCode/issues/361) [#353](https://github.com/tonsky/FiraCode/issues/353) [#348](https://github.com/tonsky/FiraCode/issues/348) [#328](https://github.com/tonsky/FiraCode/issues/328) [#326](https://github.com/tonsky/FiraCode/issues/326) [#235](https://github.com/tonsky/FiraCode/issues/235) - Atom/VS Code are known to break certain ligatures in certain syntaxes [#361](https://github.com/tonsky/FiraCode/issues/361) [#353](https://github.com/tonsky/FiraCode/issues/353) [#348](https://github.com/tonsky/FiraCode/issues/348) [#328](https://github.com/tonsky/FiraCode/issues/328) [#326](https://github.com/tonsky/FiraCode/issues/326) [#235](https://github.com/tonsky/FiraCode/issues/235)
# Corrupted font in IntelliJ on Windows ## Corrupted font in IntelliJ on Windows
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. 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](https://github.com/tonsky/FiraCode/issues/589) [#581](https://github.com/tonsky/FiraCode/issues/581) [#398](https://github.com/tonsky/FiraCode/issues/398) [IDEA-159901](https://youtrack.jetbrains.com/issue/IDEA-159901) Issues: [#589](https://github.com/tonsky/FiraCode/issues/589) [#581](https://github.com/tonsky/FiraCode/issues/581) [#398](https://github.com/tonsky/FiraCode/issues/398) [IDEA-159901](https://youtrack.jetbrains.com/issue/IDEA-159901)
# No italics/bad italics ## No italics/bad italics
Fira Code does not have italics at all. If you see italicized glyphs it means your editor is “faking” them. Fira Code does not have italics at all. If you see italicized glyphs it means your editor is “faking” them.
Issues: [#375](https://github.com/tonsky/FiraCode/issues/375) [#320](https://github.com/tonsky/FiraCode/issues/320) [#281](https://github.com/tonsky/FiraCode/issues/281) Issues: [#375](https://github.com/tonsky/FiraCode/issues/375) [#320](https://github.com/tonsky/FiraCode/issues/320) [#281](https://github.com/tonsky/FiraCode/issues/281)
# Not recognized as monospace by fontconfig (e.g. in Kitty) ## Not recognized as monospace by fontconfig (e.g. in Kitty)
See https://github.com/tonsky/FiraCode/issues/840 Issues: [#840](https://github.com/tonsky/FiraCode/issues/840)