Closed rwxmad closed 4 months ago
I'm also impacted by this. Alacritty's rendering of the font looks much better than WezTerm's to me. I'm on ArchLinux X11.
In #2927, it was suggested to use:
config.front_end = "WebGpu"
This does result in a better looking font for me but it still doesn't look quite right. Now it is bolder but a bit more smeared. I don't understand what Alacritty is doing differently but I like it much better.
This does result in a better looking font for me but it still doesn't look quite right. Now it is bolder but a bit more smeared. I don't understand what Alacritty is doing differently but I like it much better.
Absolutely agree, this is the only reason why I can't migrate from Alacritty to wezterm :(
Fonts appearance is a highly subjective topic; there are thousands of users that are happy with how the fonts appear. That doesn't mean that you are wrong, just that you find different things more important in how you perceive text.
wezterm uses freetype on all operating systems for consistency and sanity in implementation and maintenance. That makes its rasterization different from most other software that uses the macOS font renderer, because it is a different renderer.
I am not going to make wezterm use the macOS renderer.
I've exposed just about every knob and option that is possible to expose from freetype to allow users to dial in their preference, but it is admittedly a complex topic.
I do not have time to troubleshoot and dial in all the configs of every user that has questions about this, so I'm sorry to say that I'm going to close this issue without spending more time on it. It's not that I don't care, or don't think that it is important to you, but rather that there isn't anything for me to fix and working through these sorts of issues is incredibly time consuming and frustrating, and I get nothing out of the experience.
If you feel that you have to use alacritty as a result, that is fine by me: you've got to do what you've got to do.
It's subjective from an aesthetic point of view, but from an accessibility one, I find this frustrating as someone without great vision. I love everything about this terminal, and yet it's the one thing that's is the one thing stopping me from switching over 😓 https://github.com/wez/wezterm/issues/3774#issuecomment-1791730581 is a real strain on my eyes compared to other terminals, even after dialling every knob 😅 I suppose I will just have to pray for sixel support in Alacritty one day 🙏
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
wezterm 20240203-110809-5046fc22
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
With this configuration, wezterm font is completely different compared to Alacritty, its similar to:
3774, #689
Alacritty: Wezterm:
I try tune many options, but anyway don't have same result as in alacritty. Like in #689, i try to specify font directory:
But i get an error:
My Alacritty config:
To Reproduce
Case with default font specified:
Case with custom font dir:
Configuration
like in reproduce section
Expected Behavior
Font is displayed completely differently than in other terminals, in particular as in Alacritty with the same settings
Logs
No response
Anything else?
No response