You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reacted by Angelos Serpezoudis, KhalO, Davidsv, Peter Clark, ExE Boss, Marnen Laibow-Koser, Amin Ya, 1zizi1, Vlad Dyshakov, Rodrigo Garcia Martin and 1 more
Reacted by Sherlock Holo, Shimmy Weitzhandler, Mariobro85, ilinuxio, Roshan B, Chih-Yung Liang, teapot, udo-art, Alok Shandilya, juiceDeLemon and 8 more
Hm. To be honest, I think that they're sufficiently differentiated simply by their lengths, and adding a break in the middle kind of defeats the purpose of even having a ligature. I do appreciate your frustration though, and am interested to hear if others share it. For the time being I'll leave this open to see if others chime in, but do not have any intent to change it currently.
Thanks!
Reacted by Shimmy Weitzhandler, Dan Soper, Mariobro85, teapot, udo-art, 1zizi1, juiceDeLemon, Tarun Jagotra and Carey Hester
When you look at this in a big code base, in which necessarily these are not written near each other it is very hard to determine between the two. The purpose of a font should be to enhance the experience of the user, but now the user goes into a guessing game!
I want to say that this does not question the ligature usage at all. We can choose a single ligature that has a custom space in between the two =, which is not possible normally.
The same goes for _, I always wished that these were easier to detect, like:
In case you decide not to do this for the whole font, if we can have a separate patch that does not include these ligatures, that would be good too.
Reacted by Angelos Serpezoudis, Davidsv, Peter Clark, Zhu Wang and 1zizi1
Reacted by Sherlock Holo, Shimmy Weitzhandler, Mariobro85, udo-art, TamKengHong, Sagnik Bhattacharya, Đỗ Minh Đăng and Tarun Jagotra
I agree with this. I often have trouble telling a single equals sign from a double one, especially if there isn't a point of reference.
adding a break in the middle kind of defeats the purpose of even having a ligature.
I disagree. The point of ligatures is to make code easier & quicker to read. If we have to double check equals signs to make sure that there's two of them and not one, that's not very productive and it goes against the point of having them! They can also have the function of making text look prettier, but that should only be a secondary function.
Reacted by Amin Ya, Alex Yashukov, Peter Clark, ExE Boss, Marnen Laibow-Koser, 1zizi1 and juiceDeLemon
Reacted by Shimmy Weitzhandler, Mariobro85, TamKengHong, viocha, Shai Avraham, Đỗ Minh Đăng and Tarun Jagotra
I actually like the old one better.
Is there a variant or a way to force using those ligatures? Maybe instead of changing it to two separate ones make one but should span the max full width of two characters?
Reacted by Winston Liu, Sherlock Holo, ilinuxio, Mariobro85, teapot, Rick Gray, TamKengHong, juiceDeLemon, Rickard, Shai Avraham and 5 more
I'm also gonna share my sentiment here. When someone enables ligatures they want a wide assignment sign. Hence == should be displayed as a single wide character.
Reacted by Sherlock Holo, Tom Schneider, Mariobro85, rajat, teapot, udo-art, Titov Andrey, Wynell, TamKengHong, juiceDeLemon and 8 more
Activity
aaronbell commentedon Jun 1, 2020
Hm. To be honest, I think that they're sufficiently differentiated simply by their lengths, and adding a break in the middle kind of defeats the purpose of even having a ligature. I do appreciate your frustration though, and am interested to hear if others share it. For the time being I'll leave this open to see if others chime in, but do not have any intent to change it currently.
Thanks!
aminya commentedon Jun 1, 2020
When you look at this in a big code base, in which necessarily these are not written near each other it is very hard to determine between the two. The purpose of a font should be to enhance the experience of the user, but now the user goes into a guessing game!
I want to say that this does not question the ligature usage at all. We can choose a single ligature that has a custom space in between the two
=, which is not possible normally.The same goes for

_, I always wished that these were easier to detect, like:In case you decide not to do this for the whole font, if we can have a separate patch that does not include these ligatures, that would be good too.
seangelos commentedon Jun 3, 2020
I agree with this. I often have trouble telling a single equals sign from a double one, especially if there isn't a point of reference.
I disagree. The point of ligatures is to make code easier & quicker to read. If we have to double check equals signs to make sure that there's two of them and not one, that's not very productive and it goes against the point of having them! They can also have the function of making text look prettier, but that should only be a secondary function.
Make Cascadia Code a variable font w/ 6 named variations (#304)
aminya commentedon Jun 29, 2020
Thanks for fixing this!
weitzhandler commentedon Aug 6, 2020
I actually like the old one better.
Is there a variant or a way to force using those ligatures? Maybe instead of changing it to two separate ones make one but should span the max full width of two characters?
Sherlock-Holo commentedon Aug 25, 2020
the old is better
actually if someone enabled ligatures, he won't want to see there is a space between two =, otherwise, why enable the ligatures?
if someone doesn't like there's any space between two =, why doesn't he disable ligatures?
aminya commentedon Aug 25, 2020
==is just one ligature among 100s that Cascadia provides. Why disable everything just because of one?You can patch this symbol if you hate this extra space.
https://admcpr.com/automating-the-patching-of-cascadia-code-to-include-nerd-fonts/
https://github.com/gaplo917/Ligatured-Hack
Sherlock-Holo commentedon Aug 25, 2020
for people who want no space between two
=, after updating to the latest version, the==becomes unacceptedweitzhandler commentedon Aug 25, 2020
I'm also gonna share my sentiment here. When someone enables ligatures they want a wide assignment sign. Hence
==should be displayed as a single wide character.