However, it doesn't support all the characters I need, so I can't use it as a terminal font. However, I starred your repo, and will watch it.

Thanks again for the effort, it looks really nice.

Edit: I'm quite fond of the 'k'.

Hand-hinted by Fabrizio: ”More than 9000 characters optimized from 9pt to 48pt to guarantee the best possible readability.”

It is the ultimate “programmer’s font” and well worth the money for something you stare at every day and the next best thing to a bitmap font in today’s “Retina resolution” world.

Accept no imitations.

⁽¹⁾ https://fsd.it/shop/fonts/pragmatapro/

I really like using Cozette - it has great glyph support and a hi-dpi version

https://github.com/the-moonwitch/Cozette

I just wish more editors had support for true bitmap fonts! Turning off anti-aliasing on a bitmap->vector converted font is OK but not quite the same.

* https://jdebp.uk/Softwares/nosh/guide/terminal-resources.htm...

It’s similar to vector icons versus hand-drawn bitmap color icons.

As I got higher DPI monitors, I found it less hassle to use outline fonts, but I still find them preferable - given the option.

That's a really fun tool.

Lower case 'l' even extends above upper case 'G'. it missed with my brain xD

Overall it's really pretty but not a daily driver.

Your comparison says the `m` is 28% different. It's completely different. I don't know what the 28% is supposed to represent (yes, the difference in the area taken, but that's meaningless).

It's a font inspired by older terminals and "no nonsense" hardware of that era. I put its design philosophy as "it's so good that it's invisible". Using it for years now, and it feels natural and neutral.

With Gruvbox dark, it really feels like I'm using an old terminal. Like how I like it.

Bitch please… https://github.com/rbanffy/3270font.

(although I'll keep using Fira)

As one YouTuber said: it's the first time we can create (somewhat) coherent, context dependent and new content using something else than other humans.

I can't say I'm too keen on wading through piles of crap, I'm also not keen on the AI bubble and its popping nor on AI's impact on employment, but if we survive all of this, we might end up with a lot of new stuff that could actually be good. 1% of this garbage will be good, but since the entire pile will be so large, that 1% might double or more our options in various fields.

  (use-package ligature
    :ensure t
    :config
    ;; Enable specific ligatures globally across all modes:
    (ligature-set-ligatures 't '("==" "===" "!=" "->" "-->" "=>" "=="))
  
    ;; Enable individual ligatures only for specific programming modes:
    (ligature-set-ligatures '(python-mode rust-mode c-mode)
                            '("||" "&&" "::" "->" "=>" "!="))

    ;; Enable ligatures only for HTML / XML:
    (ligature-set-ligatures '(html-mode nxml-mode web-mode)
                            '("<!--" "-->" "</" "/>"))

    ;; Enable global ligature mode
    (global-ligature-mode t))

[1] https://github.com/fontforge/fontforge

I hate all of them with a passion, because they look like a glyph (i.e. "something you can erase with a single backspace") but aren't. This confuses me first, and annoys me second. "Just because we could" doesn't mean that we should.

Imagine having to use Backspace twice to erase e.g. Ö or Ñ, or being able to place your cursor halfway inside Æ.

Turns out it has smart kerning, ie. character positions are subtly adjusted to compensate for different character widths. For example, i is narrow and m is wide. That causes words like "commit" to look bad in standard monospace fonts. The m's in the middle are very densely spaced and there are wide gaps around the i.

I'll be testing Commit Mono in my editors. Maybe it will even make me switch SilverBullet back to a monospace config.