I just wrote a syntax error in javascript accidentally using =< for comparison. I couldn't tell it was wrong until i copy pasted into a chat room, because fira code produces the same symbol with both <= and =<
Is there a use for this? Can =< be made to look different or be ignored?
One of them should be made optional, yes
On Tue, Jan 31, 2017 at 12:18 AM Scott Grayson notifications@github.com
wrote:
I just wrote a syntax error in javascript accidentally using =< for
comparison. I couldn't tell it was wrong until i copy pasted into a chat
room, because fira code produces the same symbol with both <= and =<Is there a use for this? Can =< be made to look different or be ignored?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tonsky/FiraCode/issues/355, or mute the thread
https://github.com/notifications/unsubscribe-auth/AARabBT8dYqWK2YaUUqslQVb44ZuYn44ks5rXhtugaJpZM4Lxq_f
.
Can't =< be a bit like /='s ligature?
In addition, many help pages say x=<the value of x>, which is ligatured to x⩽the value of x>.
this is particularly an issue if the symbol is part of a string in something like PHP. the ligature will be present in both combinations but an error is not detectable until runtime.
What's the status of this request?
pending
The syntax key=\
In light of this, I'm curious why this still justifies the =< ligature when @tonsky has used the same argument to overrule inclusion of /\ and \/ ligatures (a good decision, I would add):
\/and/\are hard to squeese in because they would conflict with escape sequences a lot
https://github.com/tonsky/FiraCode/issues/333#issuecomment-267568194
Is it simply because it was an early decision? https://github.com/tonsky/FiraCode/commit/4af8a24ede7de7020d671f794eb5cd30c94e42da
Most helpful comment
In addition, many help pages say
x=<the value of x>, which is ligatured tox⩽the value of x>.