We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some characters shouldn't always ligate. We should probably have separate OpenType features to control language-specific behavior.
=>
≥
/=
≠
-->
<!--
More as I think of it, or as I receive comments from others...
The text was updated successfully, but these errors were encountered:
See also #6.
Sorry, something went wrong.
No branches or pull requests
Some characters shouldn't always ligate. We should probably have separate OpenType features to control language-specific behavior.
Erlang
=>
isn't an arrow; rather, it's a comparison operator. It should either not ligate or (perhaps) look more like≥
.Haskell
/=
means 'not equal'. Should its ligature look more like≠
if Haskell mode is enabled?HTML/XML
-->
isn't an arrow; it closes a comment. (But we could still handle it like Monoid does and just make a corresponding<!--
ligature.)More as I think of it, or as I receive comments from others...
The text was updated successfully, but these errors were encountered: