Live data from Hacker News

Fira Code: monospaced font with programming ligatures

github.com

21–30 of 84 posts

Re: Fira Code: monospaced font with programming ligatures

#22
post #15
post #12

Earlier quoted context omitted.

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.

It works fine under konsole 15.08.

Konsole is the only terminal emulator I could get it working with, which is annoying because I much prefer rxvt. Konsole does weird stuff with my terminal colors in tmux, so I ended up not being able to use this nice font when I tried it previously.

Re: Fira Code: monospaced font with programming ligatures

#23
post #21

Probably a silly question, but can't we just generate ttf files from this so that you can use it in any windows editor?

I think the relevant issue is whether the editor can render the OpenType ligatures (well, contextual alternates) contained in the font.

You _could_ convert to .ttf, changing the curves to TrueType-style quadratics, but they'd still have to have the OpenType substitution tables for the "ligatures" to work, and I don't think that would really improve compatibility much, if at all.

Re: Fira Code: monospaced font with programming ligatures

#24

that 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!

> I (personally) don't exactly want == to look too similar to a single =, after all!

Me, either!

Amusingly (irritatingly?), /== has separation between the = characters. :/

I... have no idea why ~= turns into ~-on-top-of-= and =~ into =-on-top-of-~ . Some of these glyphs just seem ill-advised. :(

Re: Fira Code: monospaced font with programming ligatures

#25
post #12

Really 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.

What about gVim?

Re: Fira Code: monospaced font with programming ligatures

#27

that 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!

> I (personally) don't exactly want == to look too similar to a single =, after all! Me, either! Amusingly (irritatingly?), /== has separation between the = characters. :/ I... have no idea why ~= turns into ~-on-top-of-= and =~ into =-on-top-of-~ . Some of these glyphs just seem ill-advised. :(

tilde-equals is the "inequal" operator in Lua, so I suppose that makes some degree of sense. Then again, the equals-tilde makes zero sense.

Re: Fira Code: monospaced font with programming ligatures

#28
post #22
post #15

Earlier quoted context omitted.

It works fine under konsole 15.08.

Konsole is the only terminal emulator I could get it working with, which is annoying because I much prefer rxvt. Konsole does weird stuff with my terminal colors in tmux, so I ended up not being able to use this nice font when I tried it previously.

Have you tried urxvt, by any chance?

Re: Fira Code: monospaced font with programming ligatures

#29
post #4

Earlier quoted context omitted.

They don't. The == variant is has double the width.

At least for me, monospaced fonts are very helpful for looking at column specific features. == and === are row specific, so seeing the delimiters between them makes them easier to parse on a row level for me.

`===` is triple stroked in these fonts, but that is probably not enough for you. Just saying though! :)

Re: Fira Code: monospaced font with programming ligatures

#30

"Your eye spends non-zero amount of energy to scan, parse and join multiple characters into a single logical one." citation needed

The brain is very good at turning complicated features in to abstract concepts. In fact that is mostly what some parts do. So, not clear if this actually improves things or not.

For example, the == and === look quite a bit similar in the font. You have to compare relative sizes, whereas with the normal fonts you can count the spaces.

The rest of the ligatures look pretty cool!

Post reply on HN