monoid
monoid copied to clipboard
larsenwork
Two sequential m's in OSX terminal have spacing removed
Hehe...I added this ligature months ago without telling anyone and you're the first one that has noticed it :laughing:
It's controversial but I made it to free up space and I'm leaning towards keeping it since it makes it prettier and most people don't see the "error"
Let's just keep it open for a while - other's might have an opinion on this
Good deal. My terminal was my only editor supporting the ligature, so it's only there that I noticed. Feel free to suggest a different title. I definitely find the behavior jarring, but I'd like to hear other input.
I noticed it, too :D Seems a bit odd at first glance (and the 10 following glances ;) but I got used to it pretty fast. („oh right, that thing with lots of ‚legs‘ are two m“) You wouldn't even notice the space in little font sizes, so it's a clever ligature which I'd keep.
With Monoisome it still not working in Windows:
<summary>
common
mm/
Atom:
Visual Studio:
Ugh... I'm a huge fan of everything else about this font, but this one bugs me. It took me a while to prove it wasn't caused by my OS.
@StevenACoffman I have actually already fixed this and will hopefully have time to push it this weekend 👍
Can squishing "mm" be made in to an option? I'm not at all fond of it and I've been reading it a lot recently (common, commit, summary, yammer, etc.)
I just updated to the latest from the website and I'm still seeing squished m's in Atom...
@sirlancelot last commit fixed this: https://github.com/larsenwork/monoid/issues/100#issuecomment-137658963 didn't remove the mm ligature all together but I'll see if we have room for one more hardcoded option
I removed the font, and reinstalled the latest version, but I'm still having this issue. I am missing something @larsenwork ? Am I correct to assumed it is fixed on Monoisome as well?
Monoisome on Atom:
Worked for me! @GilmarLira can you verify your font file is dated December 2015? @larsenwork Monoisome lacks the fix however.
The issue persists, but is restricted to Monoisome, as you correctly indicated @AppShipIt.
@GilmarLira and @AppShipIt it's on my to-do - just been crazy busy lately :)
Weird... downloaded Monoid from the main site yesterday and I can still see the mm ligature.
Love the font btw - reminds me of DIN 1451 :+1:
I'll add a no ligature m as styleset option in next update (regular only so far)
As for monoisome I haven't used fonticons once in the last 6 months so I'm probably not going to update that any more since fontawesome and the like is now a thing of the past.
I have same issue as @GilmarLira but worse! The glyphs are superimposed as if by XOR (maybe a Java thing)
Btw I don't see a legid programmer use for 'mm' (and 'll' and such) and vote to remove them as it distorts English text.
@MarkJeronimus did you try ss15 to see if it fixed the problem? https://github.com/larsenwork/monoid/blob/master/Utilities/Monoid-ss.fea#L69
I just tweeted about this double-m ligature -- I only notice it when I'm editing prose, to be fair, but when I am it's really distracting. I really like the font otherwise, and I'm not sure if newer versions still have this or not -- should I try re-downloading it or can I turn it off?
I've since switched to Fira Code. It has nearly everything Monoid has that I like and it doesn't have the problem with the double-m ligature: https://github.com/tonsky/FiraCode
Still an issue for me. I don't actually the m's getting merged but it gets offset into the next character making it unreadable.
Line 10 makes it appear it's pushed to the right by like 3/4 of a character.
Klakier/monoid pushed what looks like a fix but only released the TTF
