You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm aware that kitty used to support Fira Code (and indeed Fira Code was used to develop ligature support in kitty and used to work out of the box in kitty, as described in #827)
Since Fira Code as of version 2 has spacing=90, which means kitty does not recognise it as a monospace font (as I understand it this is the issue), so kitty no longer works with or supports Fira Code.
I'm wondering if there is a plan to add support for Fira Code or if, due to these recent changes, Fira Code will no longer be supported by kitty?
I note that a similar issue arose with the Iosevka font in #179, where the conclusion was that Iosevka is not a monospace font, but its Term and TermLig versions are indeed monospace, and the latter supports ligatures. To my knowledge there is no (current) version of Fira Code that has both true monospace (i.e. spacing=100) and ligatures, so a possible (probably best) solution would be to somehow modify Fira Code in a similar way to Iosevka's TermLig, adding true monospace to the ligatured font, but I am curious if this could be resolved in kitty or if supporting non spacing=100 fonts is just not possible?
The text was updated successfully, but these errors were encountered:
I'm aware that
kitty
used to support Fira Code (and indeed Fira Code was used to develop ligature support in kitty and used to work out of the box inkitty
, as described in #827)Since Fira Code as of version 2 has
spacing=90
, which meanskitty
does not recognise it as a monospace font (as I understand it this is the issue), sokitty
no longer works with or supports Fira Code.I'm wondering if there is a plan to add support for Fira Code or if, due to these recent changes, Fira Code will no longer be supported by
kitty
?I note that a similar issue arose with the Iosevka font in #179, where the conclusion was that Iosevka is not a monospace font, but its Term and TermLig versions are indeed monospace, and the latter supports ligatures. To my knowledge there is no (current) version of Fira Code that has both true monospace (i.e.
spacing=100
) and ligatures, so a possible (probably best) solution would be to somehow modify Fira Code in a similar way to Iosevka's TermLig, adding true monospace to the ligatured font, but I am curious if this could be resolved inkitty
or if supporting nonspacing=100
fonts is just not possible?The text was updated successfully, but these errors were encountered: