Skip to content

Use better == symbol #284

Closed
Closed

Description

@aminya

It is hard to distinguish between these two:

1==2
1=2

image

Borg-sans-mono has a better symbol for this:
https://github.com/marnen/borg-sans-mono
image

Activity

  1. aaronbell commented on Jun 1, 2020

    @aaronbell
    Collaborator

    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!

  2. aminya commented on Jun 1, 2020

    @aminya
    Author

    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:
    image

    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.

  3. seangelos commented on Jun 3, 2020

    @seangelos

    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.

  4. added a commit that references this issue on Jun 29, 2020
    0d01fea
  5. aminya commented on Jun 29, 2020

    @aminya
    Author

    Thanks for fixing this!

  6. weitzhandler commented on Aug 6, 2020

    @weitzhandler

    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?

  7. Sherlock-Holo commented on Aug 25, 2020

    @Sherlock-Holo

    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?

  8. aminya commented on Aug 25, 2020

    @aminya
    Author

    == 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

  9. Sherlock-Holo commented on Aug 25, 2020

    @Sherlock-Holo

    for people who want no space between two =, after updating to the latest version, the == becomes unaccepted

  10. weitzhandler commented on Aug 25, 2020

    @weitzhandler

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions