Live data from Hacker News

Monaspace

monaspace.githubnext.com

151–160 of 206 posts

Re: Monaspace

#151
post #54

It does not set the mono flag, so I had to try it with GTK2 gvim to even load the font: % ttfmono MonaspaceArgon-Regular.otf monospaced flag = 0 (0 = variable-width, otherwise = monospaced) Sadly I think that because of that flag it does not enable ligatures. I was able to see ligatures and text healing in vim running in a patched st* though. I really like it thanks! The text healing only moves the line subtly as I t…

I am having the same issue in KDE Konsole: https://imgur.com/a/Dj1HZiu

I have to explicitly set the "Show all fonts" checkbox which shows all "non monospaced" fonts.

Re: Monaspace

#152
The texture healing feature seems awesome, and supporting lots of weights, OT features, etc seems good (so long as your editor supports them, though web-based editors like vscode should). I don’t love the italic options — most of the variants only change slant. Xenon changes a little. I guess you’re meant to switch to Radon for italics but I find it looks far too scratchy, even if you increase the weight a bit (which will then not match the rest of the text). I also don’t love how all-caps text renders, though I don’t see that much all-caps at the moment.

Re: Monaspace

#153
post #150
post #4

The "Texture Healing" feature is a really smart use of OpenType features to make problematic monospace combinations look much better without breaking the grid at all. One naive way to do this would be to create ligature pairs for difficult pairs (mi, lm, etc). But instead, they seem to be selecting character alternates that fill the fixed width differently based on their surroundings.

Meh... not convinced. Once you have toggled the checkbox a few times, you start noticing inconsistencies: e.g. in the example shown by default, the second "m" in "time_limit" is obviously wider than the first one because it has more space to "grow" having "i"s on both sides. Not sure if I like this...

Also, type mimi in the first code example: the two 'm's have different width...

Re: Monaspace

#155

I'm curious what people think of the "Mix & Match" examples. Radon (the handwriting one) seems to complement the other fonts well because it's basically an italic. But all the others are so similar, with their identical metrics and whatnot, that the "authoritative docstrings" and "Copilot voice" examples are really hard to distinguish.

I really like this idea. Is this supported anywhere yet or just something for future?

Re: Monaspace

#156

Earlier quoted context omitted.

Commit Mono font does something similar and calls it “Smart kerning”. Visit https://commitmono.com/ and click on the “04 Intelligent” tab for details. In practice this is unusable. Because the width of the letters now depends on the succeeding character, the text jumps as you write it. Super annoying. Cool for reading. Awful for writing.

Unrelated, but why is it that Font marketing pages specifically always have such cool-looking demoes? I love the navigation on that site, I might steal that for my own site

Probably because if you care about typography, you care about design and you crafted that demo page with passion, instead of picking a free template with 3 columns adorned by free icons of rockets, gears and brains.

Re: Monaspace

#157
post #6

How would you configure a text editor or terminal to use different fonts based on syntax (e.g. neon for code, argon for comments)?

I've configured Neovim's syntax highlighting to make comments bold italic, and then I've configured my terminal (Kitty) to display a different font for bold italic text. Using this approach, you can use up to 4 different fonts: One for normal text, one for italic, one for bold, and one for bold italic. And the font for each group doesn't necessarily need to be that style, e.g. you can use a non-bold version for the `…

I use kitty and neovim too, would you mind sharing how you got this to work?

Re: Monaspace

#159

I'm curious what people think of the "Mix & Match" examples. Radon (the handwriting one) seems to complement the other fonts well because it's basically an italic. But all the others are so similar, with their identical metrics and whatnot, that the "authoritative docstrings" and "Copilot voice" examples are really hard to distinguish.

How do you configure different fonts? This was the first thing I wanted to try, but can't figure it out. Am I missing anything obvious?

Re: Monaspace

#160
Beautiful, but too wide. Iosevka NF lets me fit a lot more information and work comfortably in three columns of code in my Emacs on a 5K screen.
Post reply on HN