-
Notifications
You must be signed in to change notification settings - Fork 302
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
Please remove the ligature 0x #346
Comments
Hi @CodeCrazy-ywt All the discussion happen to be in this issue #98 |
OK. Great thanks! |
Forgot to mention this in the Changelog. The ligature was removed in 2.210 |
Sorry, didn't remove all the code in the 2.210. You can grab the files from latest push (2.211). It's fixed there. |
So I wonder when will v2.211 be released. |
@CodeCrazy-ywt It's released now: https://github.com/JetBrains/JetBrainsMono/releases/tag/v2.221 |
Let's return to the origin: Why do we need ligatures? Take ≤ and ≥ for example. As we all know, these two symbols represents 'less-equal' and 'greater-equal'. However, they cannot be directly typed with a keyboard, so we came up with an alternative solution -- use a combination of symbols --
<=
and>=
. However, when we see these two symbol combinations, our brains needs some time to associate them with 'less-equal' and 'greater-equal', because when we were very little, it's ≤ and ≥ , not <= and >= ,that our teachers taught us to represent these two meanings. So the original purpose of ligatures is to reduce the workload of our brains and make the code more readable.However, when it comes to
0x
, situations are different. Personally, I don't think it a good idea to turn 0x into 0×, because when we see0×ff
, we tend to think it as '0 multiplied byff
', instead of a hexadecimal number that equals the decimal number 255, which runs counter to the original purpose of ligatures. Instead, I think removing the ligature is better.In addition, I disagree with the idea of turning
0x
intohex
or so on, because it changes0x
into a completely different symbol (see0xff
,hexff
and0₁₆ff
).In summary, I think that removing the ligature for
0x
is a good idea.The text was updated successfully, but these errors were encountered: