-
-
Notifications
You must be signed in to change notification settings - Fork 972
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
Fails with unsupported pixel mode. #52
Comments
Hmm, that's strange error, its basically an invalid value being returned from freetype for rendering characters. https://www.freetype.org/freetype2/docs/reference/ft2-basic_types.html#FT_Pixel_Mode It may be that the error is harmless and can be ignored, you can try that by changing line 122 in freetype.py in the kitty source code to if False: and see if the font is rendered anyway. |
Oh well, worth a try. I tried the Hack font on my linux system, it renders fine in kitty -- dont know what else to suggest. |
I am guessing conflict with freetype-infinality, i will check it. |
After build from source last version of freetype it works. tar xf freetype-2.7.1.tar.gz && cd freetype-2.7.1
./autogen.sh
make
sudo make install
export LD_LIBRARY_PATH="/usr/local/lib;/opt/python3.5/lib"
/opt/python3.5/bin/python3.5 ../../kitty/ |
I'm not aware of anything in the kitty code that requires very new versions of freetype, but then I am not a freetype expert. What was the old version of freetype on your system? If anyone comes up with anything in freetype.c that can be changed, I'll be happy to accept a pull request. In the meantime I'm closing this issue, as I can't see anything wrong in the kitty freetype code. Feel free to re-open if I am wrong. |
After correct build can`t start kitty, fails with error:
I tried different font_family(Hack, monospace, etc).
Problem in fonts, fontconfig or something different?
System info:
The text was updated successfully, but these errors were encountered: