Live data from Hacker News

Commit Mono – Neutral programming typeface

commitmono.com

91–100 of 114 posts

Re: Commit Mono – Neutral programming typeface

#94

Earlier quoted context omitted.

It's an overly stylized affectation for a font website but everything here is mouse-accessible; I didn't use my keyboard at all. My scroll wheel works and you can click on the key buttons on the bottom and the categories on the top.

Scrolling is completely broken for both trackpads and mice scroll wheel, so no, not everything is accessible. At least not in a non-buggy way. Scrolling on a web page should never be buggy.

It works perfectly fine on my MBP.

Re: Commit Mono – Neutral programming typeface

#96

Nice! I love testing new fonts. Using wezterm and alacritty (fedora 38) they look wildly different from JetBrains Mono - specially the width/ line height, but on the website they look similar in width/line height. Anyone knows why? Any tips? Ty!

I found setting config.line_height = 1.2 (or 1.3) fixed it up for me, I had the exact same reaction as to you with the line height!

In Alacritty?

Re: Commit Mono – Neutral programming typeface

#97
post #94

Earlier quoted context omitted.

Scrolling is completely broken for both trackpads and mice scroll wheel, so no, not everything is accessible. At least not in a non-buggy way. Scrolling on a web page should never be buggy.

It works perfectly fine on my MBP.

It was fixed. Before, there were nested scroll areas, interfering with each other. Now, at least from a quick test in the 02 and 03 pages, it works better.

Re: Commit Mono – Neutral programming typeface

#98

Scrolling is completely broken on this website. There is nothing cool about implementing a silly retro navigation style, if you don't either completely disable the modern navigation, or don't fully support both. Here, we have scrollers inside scrollers inside scrollers, oh my.

Update: seems to have been fixed, at least from a quick look at the 02 and 03 pages.

Re: Commit Mono – Neutral programming typeface

#99
post #15

Earlier quoted context omitted.

It’s true, some monospace fonts have absurd ligatures enabled by default. The craziest thing I’ve seen was a single-width “fi” ligature. The only point of this ligature in proportional fonts is to prevent the dot on the ‘i’ from overlapping with the hook of the ‘f’, and that by definition can’t happen in monospace! But you madmen decided to create a single “fi” glyph, like it was a letter of its own. Imagine that on…

Unicode U+FB01 is the fi ligature as a single precombined codepoint. You're right - it doesn't make any sense to have a monospaced glyph for that ligature, or for fl or ffi or many other codepoints in the Alphabetic Presentation Forms block. But those codepoints exist, and somebody might print them to the terminal, and a terminal has to represent every non-CJK glyph as a single character cell...

> a terminal has to represent every non-CJK glyph as a single character cell...

Not necessarily. Unicode has a dedicated property called East Asian Width [1] which effectively affects the terminal rendering, and "Ambiguous" characters like arrows can be configured as full-width (because CJK users expect that). Even when the configuration itself doesn't exist, the font metric may be used to infer the glyph width in this case.

[1] https://www.unicode.org/reports/tr11/

Post reply on HN