Skip to content
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

Should we disable the ligature of "=<" ? #305

Closed
liweitianux opened this issue Nov 11, 2016 · 3 comments
Closed

Should we disable the ligature of "=<" ? #305

liweitianux opened this issue Nov 11, 2016 · 3 comments

Comments

@liweitianux
Copy link

Thanks for the great work!

In a CLI tool's help or a configuration file, it is common to come across the notation:

--config=<value>    # CLI tool help message
config=<value>      # e.g., in a sample configuration file

However, the =< is turned into the less or equal to sign as , which causes significant confusions. In addition, the both =< and <= have the same ligature, which is also a bit confusing.

Should we disable the ligature of =<, or there are better reasons to have this ligature?

Thanks!

@devkanro
Copy link

devkanro commented Dec 7, 2016

Maybe we can change the '=<' and '⩽' to ' =< ' and ' ⩽ '.

@Lawri-van-Buel
Copy link

I would say to not use this font in your terminal for this reason and others. As for the sample configure file yes it's slightly confusing but since you (a programmer) know this happens not a real issue. Just use a different editor or add a space inveteeen the '=' and '<' to see it.

@aschrab
Copy link

aschrab commented Dec 14, 2016

Other than the occurrences of this pairing noted in the original report I've been quite liking this as a terminal font.

Another issue with this ligature is that it makes it impossible to visually distinguish between <= and =<, even though many languages will treat those very differently. This could make it very difficult to spot typos.

I also don't recall ever seeing (and definitely haven't used) =< intending the meaning conveyed by the resulting glyph.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants