-
Notifications
You must be signed in to change notification settings - Fork 43
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
Kitty terminal emulator support #18
Comments
There... isn't really a useful definition of "monospaced" for people to agree on. The BDF font is specified as monospaced with the XLFD spacing property, but Kitty doesn't accept it because it wants a font considered "scalable" by fontconfig. The other fonts don't really have a way, afaict, of specifying they're monospace - it's generally based on whether the characters in the font are all the same width (and in Cozette, they explicitly aren't, because of eg. double-wide emoji), and some more black magic behind the scenes. I've found microsoft/cascadia-code#118 (comment), which might be relevant. They seem to have solved the problem of a font with mixed-width glyphs not being recognized as monospace, I'll have to try and figure out how. |
Ah, alright, I've never delved into fonts or font making so I didn't know about all the fine details. Thanks for trying though, I'm happy to test anything! |
I just realized Kitty doesn't support bitmap fonts, so this is a CozetteVector issue, which makes it much easier to fix. I suspect this might've gotten fixed in #14 and could work as of release 1.8.1. Could you try it out and let me know if it works now? |
Oh, I didn't know Kitty doesn't support bitmap fonts, but I've just tried |
Here's a related issue I opened yesterday without seeing this one kovidgoyal/kitty#2739 Without the patch, I am able to get kitty to render CozetteVector via the below configuration options However, as you can see the font is too small for my DPI. @slavfox I'm curious about what your DPI is? I'd really like to use Cozette but might go blind in the process :) |
@novcn the font in your screenshot is not Cozette, as can be seen by eg. the I'm on a HP Omen X35, 3440x1440 over 35", which comes down to 106.55 PPI. My laptop is 15" 1080p, for 146.86 PPI. I like small fonts :D If you're looking for a larger bitmap font that still has solid powerline support, I can't recommend Tamzen enough. It's too big for my taste, but might be perfect for you. I'll add a note with some larger bitmap fonts to the README, since this seems to be a common question. Making a bitmap font with this many glyphs is a lot of work - unlike vector fonts, which can be auto-patched for Nerd Fonts support, I draw each character by hand. I doubt I'm ever going to make larger variants of Cozette for that reason, so the least I can do is refer to some excellent larger bitmap fonts :) |
I think this has to do with your command line. You should probably specify |
@slavfox thanks for the info! I'll give Tamzen a shot sometime. Kitty was indeed falling back to I was able to get kitty to load
|
Damn, I really wanted this to work, but I tried it as well and it just... doesn't 😞 Not really sure why, I built both |
I'd like to leave this open until (if) bitmap font support gets merged into kitty master. Cozette bitmap should work correctly on the new branch, Cozette Vector still doesn't look right in @novcn's screenshot - the bottoms of the glyphs are cut off, although I suspect that's just a Kitty configuration issue, I'd try playing with Compare eg. To the bitmap version, which renders correctly: As far as I can tell, bitmap @TheAvidDev I didn't realize I never asked for this - are you on Linux or MacOS? novcn is on Mac, so this might be a system-specific problem (kitty uses coretext rather than fontconfig on Mac). |
I'm actually on Linux @slavfox |
I'm on
Do you mean the |
Based on the creator of Kitty's comment here kovidgoyal/kitty#97 (comment) it doesn't look like bitmap font support will be merged into kitty master FYI. I'll mess around with the kitty config in a bit to fix Cozette Vector rendering. |
Ah, my bad! I assumed it was Mac because of the I also misread that fork as being a branch on the upstream Doesn't really look like I can do much more here - I'll add a note about mainline Kitty being incompatible, and a link to the fork, to the README tomorrow, and close this, in that case 😞 |
Yep, a note about a potential workaround would make sense. |
Also about that fork, it doesn't look like that's going to be up forever, a link to the specific commit in that fork is probably wiser in the long term. |
I'm also on Arch @TheAvidDev Here's some more info on my set-up in case it helps you.
I built Cozette from source off #!/bin/bash
fonts_base="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
cd $fonts_base
for font in `ls -d */ | sed 's/\///g'`; do
echo "found font $fonts_base/$font"
xset +fp $fonts_base/$font
done
xset fp rehash
fc-cache
fc-cache -fv
cd - Not sure if this is the best way to do things, but worked for me. |
Thanks, I'll try it out soon. |
I've added notes on |
Looks good, I also use alacritty and it works great, it's just slow when starting which is why I'd like to switch to kitty. But the rejection of bitmap makes me want to use it less and less. |
Hello, sorry to bump but I published an AUR package with a patch that allows Cozette (otb) to be used. |
Thanks, I'll try it out -- Edit: Whoops, looks like I didn't read carefully. |
Updated the README; thank you! |
Kitty will NEVER render the font you specify because the program author has determined he knows better what certain glyphs should look like. |
I'm not sure if this font is considered monospace*, but if it is, then it doesn't get recognized by
kitty
. Thekitty
terminal emulator is quite picky about what it takes as a monospaced font and it doesn't detect Cozette. A list of fonts that it deems acceptable can be listed withkitty list-fonts
.Here's three issues for reference and possible solutions (it seems a common one is the font's
Spacing
parameter): kovidgoyal/kitty#827, kovidgoyal/kitty#557, and ryanoasis/nerd-fonts#268Regardless of the resolution, thanks for the beautiful font!
*If this font isn't meant to be monospaced, feel free to close this issue.
The text was updated successfully, but these errors were encountered: