Nerd-fonts: Unexpected Characters in FiraCode Nerd Font Mono

Created on 4 Feb 2020  Â·  4Comments  Â·  Source: ryanoasis/nerd-fonts

🎯 Subject of the issue

The FiraCode Nerd Font Mono appears to have a problem in the latest release (v2.1.0) that did not exist in v2.0.0. The FiraCode Nerd Font appears to be unaffected. I have attached screenshots of both below for comparison.

A few examples of the issues I'm seeing in FiraCode Nerd Font Mono v2.1.0:

  • i displays as j if proceeded by f (files displays as fjles)
  • : displays as ( when adjacent to a number or ( or )
  • - displays as ≪ when adjacent to a letter

There are too many examples to list them all here. The screenshots below show more examples.

🔧 My Setup

  • _Which font are you using (e.g. Anonymice Powerline Nerd Font Complete.ttf)?_

    FiraCode Nerd Font Mono

  • _Which terminal emulator are you using (e.g. iterm2, urxvt, gnome, konsole)?_

    Terminal.app

  • _Are you using OS X, Linux or Windows? And which specific version or distribution?_

    macOS 10.15.3

★ Screenshots

FiraCode Nerd Font

Screen Shot 2020-02-04 at 12 27 48 PM
Screen Shot 2020-02-04 at 12 25 18 PM

FiraCode Nerd Font Mono

Screen Shot 2020-02-04 at 12 24 01 PM
Screen Shot 2020-02-04 at 12 25 46 PM

All 4 comments

I'm also seeing this issue

Started seeing this too recently - switching to FiraCode Nerd Font looks better for me. Just reading around the subject and see - https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/FiraCode - "By the Nerd Font policy, the variant with the 'Mono' suffix is not supposed to have any ligatures. Use the non-Mono variants to have ligatures". Maybe firacode, nerd, mono and ligatures are never meant to mix. When I use FiraCode Nerd Font mono in iterm and disable ligatures, the text renders OK, albeit without ligatures.

If you installed this font with Homebrew, running the following command may fix your issue:

brew cask reinstall font-firacode-nerd-font-mono

I'm no longer seeing this problem after reinstalling the font.

Seems like I can close this issue. Anyone still having the problem?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

maxwellmckinnon picture maxwellmckinnon  Â·  3Comments

logarytm picture logarytm  Â·  5Comments

lilyball picture lilyball  Â·  5Comments

ryanoasis picture ryanoasis  Â·  6Comments

IsOverThere picture IsOverThere  Â·  6Comments