Fira Code: monospaced font with programming ligatures
11–20 of 84 posts
Re: Fira Code: monospaced font with programming ligatures
#12Really cool, but what, if any, are the plans to get it working with Vim? It's the universal editor you're likely to find everywhere.
Re: Fira Code: monospaced font with programming ligatures
#13= vs == vs === seems like a sure way to have bugs.
Re: Fira Code: monospaced font with programming ligatures
#14Probably not possible with ligatures/glyph variants but really cool would be grouping of numbers: In groups of three the first digit would be moved to the right and the last one to the left to simulate a narrow space as thousands separator.
I suspect that it's possible, but would require an impractical number (1000) of ligatures in the font.
1 000 000
and not do: 100 000 0
assuming its parsed left to right?Re: Fira Code: monospaced font with programming ligatures
#15Really cool, but what, if any, are the plans to get it working with Vim? It's the universal editor you're likely to find everywhere.
Vim isn't there problem, it's your terminal. There is an open feature request with iterm2, but terminal.app is probably a lost cause. I know nothing about the state of Unicode font rendering in Linux.
Re: Fira Code: monospaced font with programming ligatures
#16Re: Fira Code: monospaced font with programming ligatures
#17= vs == vs === seems like a sure way to have bugs.
Re: Fira Code: monospaced font with programming ligatures
#18Re: Fira Code: monospaced font with programming ligatures
#19that looks amazing, but I kinda wish that certain ligatures were optional (which they might be, need to look at the CSS docs again for atom) I (personally) don't exactly want == to look too similar to a single =, after all!
They don't. The == variant is has double the width.
Re: Fira Code: monospaced font with programming ligatures
#20that looks amazing, but I kinda wish that certain ligatures were optional (which they might be, need to look at the CSS docs again for atom) I (personally) don't exactly want == to look too similar to a single =, after all!
They don't. The == variant is has double the width.