-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Font Aliasing #2053
Comments
Screenshots Desktop (please complete the following information):
|
Screenshot shows VSCode in foreground and VSCodium in background. Both have font aliasing set to antialiased. MacOS 15.0.1 M2 arm64 Didn't use App Manager |
The VSCode's one seems be in bold. Can you check the tokens? I don't have the issue on my macOS x86. |
I'd guess you're not seeing it because your screen is hi-dpi. I'm using a 4k 32" monitor which I run at native resolution. Mac's can render the display at a higher resolution and then scale down to native to give sharper appearance which also makes antialiasing unnecessary. Inspect editor tokens and scopes does nothing because there are no tokens in that plain text file (No grammar or semantic tokens available.) |
Sadly no. Just a plain 27' at 1440p on macOS 11. But from what I searched on the net, antialiased text shouldn't appear to be bold. |
It's ok, I can live with it. Thanks anyway |
I noticed a difference in the appearance of Font Aliasing between VSCode and VSCodium. When "workbench.fontAliasing": "antialiased" the appearance is noticeably different. I can live with default instead but it was a surprising difference coming from VSCode.
The text was updated successfully, but these errors were encountered: