You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello! since switching from terminal Vim to MacVim, I've noticed that fl and fi render improperly, making text such as fixme, fluid, and config illegible and messing up the rest of the line.
within MacVim, a similar issue has been raised for a different font, albeit for different characters: macvim-dev/macvim#841
I have been unable to replicate this issue with any other font on my machine that uses ligatures, so I'm curious as to whether this is not a MacVim-specific rendering problem, whether similar behavior can be replicated, and whether this is the correct place to make note of it.
given the discussion on whether the ligatures in question should be included at all, this issue slightly relates to: #1
thanks!
Screenshots
set macligatures
set nomacligatures
The text was updated successfully, but these errors were encountered:
Kudos for being one of the Vim people! Every time I try a derivative, I think "gee, I'll have to use a year to learn how to get productive using this". 😆
MacVim has problems drawing more of this font's ligatures, it seems (eg. >= and <=).
It will probably work better if I change the way ligatures are set up. At the moment, I don't have an ETA on this.
thanks for getting back to this so quickly! I figured this had more to do with MacVim than anything given that everything renders hunky-dory in iTerm2:
Background
hello! since switching from terminal Vim to MacVim, I've noticed that
fl
andfi
render improperly, making text such asfixme
,fluid
, andconfig
illegible and messing up the rest of the line.within MacVim, a similar issue has been raised for a different font, albeit for different characters: macvim-dev/macvim#841
I have been unable to replicate this issue with any other font on my machine that uses ligatures, so I'm curious as to whether this is not a MacVim-specific rendering problem, whether similar behavior can be replicated, and whether this is the correct place to make note of it.
given the discussion on whether the ligatures in question should be included at all, this issue slightly relates to: #1
thanks!
Screenshots
set macligatures
set nomacligatures
The text was updated successfully, but these errors were encountered: