Arch Linux

frabjous

Member

Registered: 2010-07-13

Posts: 367

[SOLVED] otf-fira-code 2-1 incompatible with kitty, possibly others

It appears that the new versions of the fira-code packages (2-1; released last week) create a problem with some terminals, including kitty, which I'm using, which don't recognize them as monospaced fonts. Running the command

kitty list-fonts

Lists other monospaced fonts, but not Fira Code.

I'm using otf-fira-code, but I think the same problem arises for ttf-fira-code.

(If someone is using gnome terminal and can test there, I'd appreciate it. gnome-terminal does not work on my setup, for other reasons I should investigate...)

Judging from the discussion on the kitty bugtracker here, I'm guessing this is because the new versions of the fonts have a spacing value of 90, and a value of 100 is expected for monospaced fonts, that is, with the new packages:

$ fc-list -v "Fira Code" | grep spacing | head -n 1
        spacing: 90(i)(s)

Downgrading to the previous version, otf-fira-code 1-207, solves the problem, and then:

$ fc-list -v "Fira Code" | grep spacing | head -n 1
        spacing: 100(i)(s)

I'm not 100% sure who I should report this bug to... The general Fira Code upstream github? The Arch package maintainer? Somewhere else? Thoughts?

Last edited by frabjous (2019-09-17 16:50:53)

frabjous

Member

Registered: 2010-07-13

Posts: 367

Re: [SOLVED] otf-fira-code 2-1 incompatible with kitty, possibly others

It appears this was something between a bug and a feature, as spacing=90 signifies "mixed" between monospaced and not, but the next version of kitty will support these fonts, and the patch is already working in kitty-git in the AUR, which I've switched to at least until the version of kitty in the main repos is updated. See here.

Making as solved.