larsenwork / monoid

Customisable coding font with alternates, ligatures and contextual positioning. Crazy crisp at 12px/9pt. http://larsenwork.com/monoid/
7.85k stars 170 forks source link

javascript: support for === and !=== #194

Open trevorhibblen opened 6 years ago

trevorhibblen commented 6 years ago

sorry if this has already come up. I really love this font, tho i write mostly js code.

in javascript it's common to use triple equals for "strict" equality:

ex:

true: 1 == '1'
false: 1 === '1'
true: 1 !== '1'

javascript is truly magical.

currently the first two == and != leave a dangling=.

to keep it from conflicting, maybe the triple lined mathematical equivalence/identical-to would fit:

true: 1 ≡ 1
false: 1 ≢ 1
balupton commented 6 years ago

I'd love this. As it does look quite sore. Is my only complaint about this font.

screen shot 2018-02-15 at 1 48 49 pm
balupton commented 6 years ago

could be a dupe of https://github.com/larsenwork/monoid/issues/151

balupton commented 6 years ago

works in fira code

screen shot 2018-02-15 at 1 55 13 pm

but not hasklig

screen shot 2018-02-15 at 1 54 59 pm
joshburgess commented 6 years ago

I thought at one time this actually worked, but I could be mistaken. I can confirm though that ==, ===, and !== do not render as ligatures in Atom right now.

!= does render as a ligature, but leaves a dangling = when written as !==.

I'd like to see support for this, as I prefer Monoid over Fira Code.

joshburgess commented 6 years ago

So, I just checked my windows gaming desktop, which has an older version of Monoid installed compared to what I have installed on OSX on my Macbook Pro, and it actually does have ligatures for !== and ===.

What happened? Is this a problem with a newer version of the font? Or is this a problem with MacOS/OSX vs Windows?

We should try to get this fixed. Monoid is nicer looking than Fira Code when these are working, IMO. :)

image

balupton commented 5 years ago

@larsenwork if we set a bounty to get this fixed, how much would be enough?

d-cas commented 4 years ago

=== works in atom and sublime but not vs code

idahogurl commented 2 years ago

The characters are actually missing in the Retina version. Switching to the Regular version fixed my issue. Though it'd be nice for the Retina version to work.