Closed envp closed 3 years ago
https://sw.kovidgoyal.net/kitty/faq/#kitty-is-not-able-to-use-my-favorite-font
And there is no need to use patched fonts in kitty, in fact, you should not use them as patching often breaks fonts. Instead use https://sw.kovidgoyal.net/kitty/conf/#opt-kitty.symbol_map with the nerd fonts installed as a standalone font.
Thanks for the response, but the issue persists after switching to the unpatched font (installed per instructions here: https://github.com/be5invis/Iosevka)
I confirmed that both Iosevka Fixed
, and Iosevka Term
both show up in fontconfig like so:
fc-list : family spacing outline scalable | grep -e spacing=100 -e spacing=90 | grep -e outline=True | grep -e scalable=True | grep -i iosevka
...
Iosevka Fixed:spacing=100:outline=True:scalable=True
...
Iosevka Term:spacing=100:outline=True:scalable=True
...
and also in kitty +list-fonts
.
As I understand it, it this is unexpected behaviour from kitty
, and the issue still exists (also happens with other unpatched fonts such as 'IBM Plex Mono')
Works fine for me:
kitty --config NONE -o 'font_family Iosevka Term' --debug-font-fallback
[276 07:09:26.694468] Preloaded font faces:
[276 07:09:26.694501] normal face: /usr/share/fonts/TTF/iosevka-regular.ttc:1
[276 07:09:26.694511] bold face: /usr/share/fonts/TTF/iosevka-bold.ttc:1
[276 07:09:26.694519] italic face: /usr/share/fonts/TTF/iosevka-regular.ttc:9
[276 07:09:26.694527] bi face: /usr/share/fonts/TTF/iosevka-bold.ttc:9
Works fine for me:
kitty --config NONE -o 'font_family Iosevka Term' --debug-font-fallback [276 07:09:26.694468] Preloaded font faces: [276 07:09:26.694501] normal face: /usr/share/fonts/TTF/iosevka-regular.ttc:1 [276 07:09:26.694511] bold face: /usr/share/fonts/TTF/iosevka-bold.ttc:1 [276 07:09:26.694519] italic face: /usr/share/fonts/TTF/iosevka-regular.ttc:9 [276 07:09:26.694527] bi face: /usr/share/fonts/TTF/iosevka-bold.ttc:9
Yeah, launching it as a child process works fine for me as well. What I meant was, when I launch it through the system launcher it doesn't pick up the font in the config, any reason you'd expect them to behave differently (and how would one go about debugging this)?
Presumably your system launcher is either launching kitty with a different set of env vars or a different kitty, if you have multiple ones installed on your system. I have no clue how to debug your system launcher, presumably look for its log files if any and figure out what its doing.
Presumably your system launcher is either launching kitty with a different set of env vars or a different kitty, if you have multiple ones installed on your system. I have no clue how to debug your system launcher, presumably look for its log files if any and figure out what its doing.
To clarify, I have a single installation of kitty from brew
, which is I why I think the issue is with kitty.
If I change the font to e.g. Fantasque Sans Mono
it loads the correct font (on startup, as well as on change), this only happens with some fonts.
I'll try the curl -L https://sw.kovidgoyal.net/kitty/installer.sh | sh /dev/stdin
from docs and get back on this issue.
I'll try the
curl -L https://sw.kovidgoyal.net/kitty/installer.sh | sh /dev/stdin
from docs and get back on this issue.
Issue persists with a binary install as well.
There are no env vars that will affect some fonts and not others. One or more of your assumptions is incorrect, figure out which one.
Have you resolved this one? @envp
@kovidgoyal still, it shows me Symbol map: Symbols Nerd Font is invalid, ignoring
even though it's present
Read the FAQ
Read the FAQ
I did it as it was suggested in the FAQ. Here is the config.
And here is the output
Separate symbols font and not patched font. Symbols are broken and show something in chinese
Read the FAQ again, in particular focus on the syntax for symbol_map
Read the FAQ again, in particular focus on the syntax for symbol_map
Oh, got it. So I must specify the codepoints. Thanks!
There are no env vars that will affect some fonts and not others. One or more of your assumptions is incorrect, figure out which one.
Apologies for the notification on a closed issue, but the resolution in my case turned out to be the macOS process lingering. I did not explicitly quit (Cmd + Q
) kitty, which is the root cause. I've edited the issue description with what resolved the issue in my case.
Is it possible to mark this under some kind of user-error label?
Describe the bug
kitty
doesn't load font specified byfont_family
inkitty.conf
, unless provided as an override on the CLI (but still complains about not being able to find it, despite loading it)To Reproduce Steps to reproduce the behavior:
font_family IosevkaNerdFontCompleteM-Term
, orfont_family Iosevka Nerd Font Mono Regular
inkitty.conf
kitty
defaults to OS monospace font (Menlo in my case), expected it to load the specified fontEnvironment details
Additional context Output of
kitty +list-fonts --psnames | grep -i iosevka
Running
kitty --config NONE -o font_family='Iosevka Nerd Font Mono Regular'
does the following (unexpected things):Kitty says the font isn't found.
But the newly opened child window uses Iosevka.
Additionally,
kitty --config NONE
usesMenlo
as expectedResolution:
User must quit kitty. In my case the default behaviour of macOS is not to quit on close, this is OS dependent and not a bug in kitty.