Open coolCucumber-cat opened 1 year ago
It used to be like that and there were issues with people confusing ==
for =
, leading to the break being added for better clarity. see: https://github.com/microsoft/cascadia-code/issues/284
I agree it could be a stylistic set, though, and will give that some thought.
A lot of people on that issue were complaining about it too and the one thanking for the change got 11 thumbs down and 1 up. Plus if you don't like it, you can turn it off or there can be an option for it.
Description of the new feature/enhancement (with images if possible)
So the ===, the !== and the != all have a ligature that joins the symbols together, I find it looks quite strange for just the == to be closer, but still not joined. Is it on purpose so you don't get it confused with a = ? Just my opinion but it would look cleaner that way.
Proposed technical implementation details
Either it could be part of the main ligatures or it could be its own separate own just like slashed zero. So in VSCode you could do:
"editor.fontLigatures": "'zero', 'equals'"
maybe, so that it's there if you want it. Also maybe could there be a ligature for => that isn't completely different to just a = and a > ?