Skip to content
Discussion options

You must be logged in to vote

The fact that kitty --config NONE gives you a weird non-monospaced font is the big clue here: kitty asks fontconfig for the monospace family and for emoji fallback, so if fontconfig's resolution is broken on your system, kitty breaks even with no config. Other terminals may not be affected because they don't rely on fontconfig the same way.
A few things to try, in order:

1 - See what kitty actually picks for emoji:

kitty --debug-font-fallback
then type/paste an emoji in that window and check the terminal you launched it from — it prints which font gets selected for each glyph.

2- Check what fontconfig resolves:

fc-match monospace
   fc-match emoji

If monospace resolves to something weir…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by ExpandingMan
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants