-
Notifications
You must be signed in to change notification settings - Fork 304
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
Safe stylistic ligatures #287
Comments
It looks like there is still no documentation for all alternatives ( #8 (comment) ). Looks like it is hidden under the name "editor.fontLigatures": "'ss19' 1, 'zero' 1" Were all currently existing ligatures considered for whether they fit the scope of this issue? |
Hi @KillyMXI
|
I mostly care about #11 and have ligatures off wherever I can until that one is fulfilled. So, I'm not deeply familiar with all ligatures.
("stencil bridge" is actually a good analogy for what I'd like to see more in #11, to have all characters aligned but discrete.) |
stylistic ligatures are meant to improve both code readability, and code writing.
These are, I think, primary goals of ligatures for monospaced code aware fonts like this one.
The cosmetic aspect is of last resort (and always subjective).
According to these principles, this issue is not at all about wether a ligature is beautiful or not.
When a ligature changes the perceived order of symbols, it goes against code writing.
When a ligature make it not clear what symbol is used, it goes against code readability, and code writing.
Below are some examples as such ligatures that could be reworked to improve either code readability, code writing or both:
!==
The current result seems to indicate that the input is
=/=
There are 2 drawbacks:
it seems the input is using a
/
instead of a!
when you select the first character of the ligature,
your selection appears to be a
=
character while it is in fact a!
!=
same problem as!==
Note: this issue is extracted from #11
The text was updated successfully, but these errors were encountered: