Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update terminal doesn't use font #1325

Closed
LamprosPitsillos opened this issue Dec 4, 2021 · 10 comments
Closed

After update terminal doesn't use font #1325

LamprosPitsillos opened this issue Dec 4, 2021 · 10 comments

Comments

@LamprosPitsillos
Copy link

❯ fc-list | rg "Fira"        
/usr/share/fonts/TTF/FiraMono-Bold.ttf: Fira Mono:style=Bold
/usr/share/fonts/TTF/FiraCode-SemiBold.ttf: Fira Code,Fira Code SemiBold:style=SemiBold,Regular
/usr/share/fonts/TTF/FiraMono-Regular.ttf: Fira Mono:style=Regular
/usr/share/fonts/TTF/FiraCode-Retina.ttf: Fira Code,Fira Code Retina:style=Retina,Regular
/usr/share/fonts/TTF/FiraCode-Bold.ttf: Fira Code:style=Bold
/usr/share/fonts/TTF/FiraCode-Light.ttf: Fira Code,Fira Code Light:style=Light,Regular
/usr/share/fonts/TTF/FiraCode-Medium.ttf: Fira Code,Fira Code Medium:style=Medium,Regular
/usr/share/fonts/TTF/FiraMono-Medium.ttf: Fira Mono,Fira Mono Medium:style=Medium,Regular
/usr/share/fonts/TTF/FiraCode-Regular.ttf: Fira Code:style=Regular
#: Fonts {{{

#: kitty has very powerful font management. You can configure
#: individual font faces and even specify special fonts for particular
#: characters.

 font_family      Fira Code Retina
 bold_font        auto
 italic_font      JetBrains Mono SemiBold Italic
 bold_italic_font auto

Terminal: Kitty version 0.23.1

@Arthur-Stewart
Copy link

Arthur-Stewart commented Dec 5, 2021

Same issue on Arch Linux after upgrading to ttf-fira-code 6.1-1. When I ran kitty list-fonts under the Fira Code section I only saw 2 font options.

Fira Code Bold
Fira Code Light

The other four font options (medium, regular, retina, semibold) were missing.

Downgrade to 5.2.1 still works.

kitty 0.23.1

@tonsky
Copy link
Owner

tonsky commented Dec 5, 2021

Anyone has ideas why is this happening? Is there a kitty ticket?

@idest
Copy link

idest commented Dec 5, 2021

@tonsky this is similar to #840 #1000 and #1073, I was able to fix it with the workaround detailed in https://sw.kovidgoyal.net/kitty/faq/#kitty-is-not-able-to-use-my-favorite-font

@oeyoews
Copy link

oeyoews commented Dec 6, 2021

@idest I try it, but it's no effect for me. so, i downgrade it's verson to 5.2. it's good.

@nikatar
Copy link

nikatar commented Dec 6, 2021

@idest, thank you, it's work
@Arthur-Stewart, i confirm this problems on arch after updatring

@morne
Copy link

morne commented Dec 6, 2021

I had the same issue as @Arthur-Stewart , also on Arch Linux. Downgrading to 5.2.1 works.

@kjerstadius
Copy link

I've also encountered this issue after upgrading to Fira Code 6.1 on Arch Linux. After reading the kitty faq article linked above I decided to compare the spacing detected by fontconfig for 5.2 and 6.1.

5.2

fc-list : family spacing outline scalable | rg Fira
Fira Code:spacing=90:outline=True:scalable=True
Fira Code,Fira Code Retina:spacing=90:outline=True:scalable=True
Fira Code,Fira Code Medium:spacing=90:outline=True:scalable=True
Fira Code,Fira Code Light:spacing=90:outline=True:scalable=True
Fira Code,Fira Code SemiBold:spacing=90:outline=True:scalable=True

6.1

fc-list : family spacing outline scalable | rg Fira
Fira Code:spacing=100:outline=True:scalable=True
Fira Code:outline=True:scalable=True
Fira Code,Fira Code Retina:outline=True:scalable=True
Fira Code,Fira Code Medium:outline=True:scalable=True
Fira Code,Fira Code Light:spacing=100:outline=True:scalable=True
Fira Code,Fira Code SemiBold:outline=True:scalable=True

As can be seen several variants are missing the spacing value in 6.1 and I'd bet that's why kitty doesn't pick up (for example) the Retina variant. @tonsky Any idea why this would be?

tonsky added a commit that referenced this issue Dec 6, 2021
@tonsky
Copy link
Owner

tonsky commented Dec 6, 2021

Hopefully fixed in 6.2, please check. Somehow Glyphs keeps changing random glyphs widths even if I don’t touch them. Added extra check before release

@BigMikeM
Copy link

BigMikeM commented Dec 7, 2021

I had the same issue; 6.2 fixed it for me! Thank you!

@tonsky tonsky closed this as completed Dec 7, 2021
@kjerstadius
Copy link

@tonsky Thanks for the quick turnaround on the fix!

br3ndonland added a commit to br3ndonland/dotfiles that referenced this issue Oct 13, 2024
This commit will update `kitty.conf` to switch the font from Dank Mono
to Recursive (`Rec Mono Duotone`).

This commit is part of a switch from Dank Mono to Recursive.
Although Dank Mono does render in VSCode, it is not correctly monospaced
and therefore stopped working in some applications that have more strict
font requirements, like the terminal emulator kitty (kitty >=0.36).

https://www.recursive.design/
https://github.com/arrowtype/recursive
https://sw.kovidgoyal.net/kitty/changelog/
https://sw.kovidgoyal.net/kitty/faq/#kitty-is-not-able-to-use-my-favorite-font

Explanation from Dank Mono creator Phil Pluckthun via email:

> Some terminal applications require a specific monospace flag to be set
> in the font file that was only gaining traction after the font was
> released. Some also just don't support fonts with ligatures. In Dank
> Mono's case the specific flag that some applications require to select
> the font as a monospaced one simply isn't set, and a different, older
> one is set instead.

Related issues:

eigilnikolajsen/commit-mono#15
IdreesInc/Monocraft#26
IdreesInc/Monocraft#77
tonsky/FiraCode#1325
vercel/geist-font#33
br3ndonland added a commit to br3ndonland/dotfiles that referenced this issue Oct 13, 2024
This commit will update the README to document the switch from Dank Mono
to the Recursive font (`Rec Mono Duotone`).

Although Dank Mono does render in VSCode, it is not correctly monospaced
and therefore stopped working in some applications that have more strict
font requirements, like the terminal emulator kitty (kitty >=0.36).

https://www.recursive.design/
https://github.com/arrowtype/recursive
https://sw.kovidgoyal.net/kitty/changelog/
https://sw.kovidgoyal.net/kitty/faq/#kitty-is-not-able-to-use-my-favorite-font

Explanation from Dank Mono creator Phil Pluckthun via email:

> Some terminal applications require a specific monospace flag to be set
> in the font file that was only gaining traction after the font was
> released. Some also just don't support fonts with ligatures. In Dank
> Mono's case the specific flag that some applications require to select
> the font as a monospaced one simply isn't set, and a different, older
> one is set instead.

Related issues:

eigilnikolajsen/commit-mono#15
IdreesInc/Monocraft#26
IdreesInc/Monocraft#77
tonsky/FiraCode#1325
vercel/geist-font#33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants