Last active
August 16, 2024 09:02
-
-
Save MTuner/3ee1e24b58808b2cd6b17c3a176b832e to your computer and use it in GitHub Desktop.
Fixing font rendering/aliasing in Sublime Text in MacOS Mojave
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Apple removed colored sub-pixel antialiasing in MacOS Mojave | |
| (https://developer.apple.com/videos/play/wwdc2018/209/ starting from ~28min) | |
| To make fonts look normal in Sublime Text, add to Preferences: | |
| // For the editor | |
| "font_options": [ "gray_antialias" ], | |
| // For the sidebar / other elements | |
| "theme_font_options": [ "gray_antialias" ], |
Thank you, I've been suffering with this for months.
Oh wow, this helped me on Linux as well! Thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The original Gist does not make sense to me.
Sub-pixel AA (i.e. coloured fringes) is what we want, and what was the default in macOS 10.13 and before. So why explicitly set Sublime to use Greyscale AA? That's just doubling down on choosing worse AA (explicitly setting it in Sublime even though it's what macOS 10.14 does out of the box anyway).
When using the "defaults write" mechanism, rather than affecting every app on the system, I think it's better to scope it to only affect particular apps you have issues with, e.g.
# Re-enable sub-pixel (as opposed to only greyscale) font AA on macOS 10.14+ defaults write com.sublimetext.3 CGFontRenderingFontSmoothingDisabled 0p.s. It's not worth doing the above if you use a Retina/HiDPI display. Greyscale font AA looks fine at high DPI, which is probably why Apple chose to make their change. Though, I don't understand why they didn't limit it to only when a Retina display is being used.