Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Monaspace

monaspace.githubnext.com

Post reply on HN
Print view View original

171–180 of 206 posts

Re: Monaspace

#171

Post by nielsbot »

peebeebee wrote: post #109
nielsbot wrote: post #107

Seems like in modern times, on modern systems, we can move beyond monospaced fonts for code. I have recommended this many times here, but I use a proportional coding font: Input Sans https://input.djr.com

What are the reasons for your recommendations? One problem I might see is that it is even harder to spot a typo with this font.

For me, I think proportional fonts are the way text was meant to seen, and monospaced fonts exist to accommodate the limitations of computers, printers and typewriters.

Why is that? In text or punctuation?

For words it’s more readable. The punctuation is designed for coding. The numerals are still monospaced.

Re: Monaspace

#172

Post by nielsbot »

mcny wrote: post #108
nielsbot wrote: post #107

Seems like in modern times, on modern systems, we can move beyond monospaced fonts for code. I have recommended this many times here, but I use a proportional coding font: Input Sans https://input.djr.com

Does it support ligatures such as >= to ≥? I tried the web preview on a phone maybe it is a limitation of Firefox on Android? For others, this is ligatures https://fonts.google.com/knowledge/glossary/ligature

I don’t think so? I personally don’t use that feature :)

Re: Monaspace

#173

Post by jskherman »

tmtvl wrote: post #166
jskherman wrote: post #79

I'm bothered by the Rd symbol of Radon on the page, it's should be Rn. It makes me double-check if there's actually an element that's not Radium (Ra), not Radon (Rn), but also starts with an R and has a d in its name.

Rhodium, but that's Rh.

Neat, one more element to the "Rd" element group.

Re: Monaspace

#174

Post by graypegg »

whalesalad wrote: post #30
csande17 wrote: post #13

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.

tbh this immediately popped into my mind before scrolling down the page - having a handwritten comment is neat and adds another differentiation to reduce strain when browsing code. some will hate it, but personally I want to try it.

I've loved Victor Mono [0] Italic for this reason for years! I find prose much easier to read with some slight joined-up lettering, which I totally concede is a 100% personal. Worth a look as well though!

[0] https://rubjo.github.io/victor-mono/

Re: Monaspace

#175

Post by stevage »

I'm confused that Neon and Argon are described as "sans" when they seem to have serifs? See the bottoms of the i and r for instance.

Re: Monaspace

#176

Post by BitFlogger »

threePointFive wrote: post #39
dpc_01234 wrote: post #5

I was initially thinking ... "OK, another monospace font (family), look nice", until I got to "texture healing" which really made me want to try it out. I really like the idea of using different style of font for different things, but as primarily terminal user, I don't even know which terminals support it (if any), and then we would need CLI text editors support as well. But I think it's a great idea.

Theoretically, anything based on xterm should have the capability for it. ESC[ m is the escape sequence to pick font 0-9. In practice though, is a different question. I use Alacritty, but I cannot find if this is supported and trying to do it myself isn't getting any results.

Texture healing requires ligatures (specifically `calt`) and Alacritty does not support ligatures.

Re: Monaspace

#178

Post by stevage »

omnimus wrote: post #135
lionkor wrote: post #114

Earlier quoted context omitted.

thats not what it does - it maintains monoSPACE while chaning the characters to not look the same width -- the best of both worlds, if anything

Its ok but instead of uneven spacing you get uneven character widths. It might be ok but there is a reason why type designers make every character to be the same and try to balance everything including spacing. Monospaced fonts designs are dictated exactly by that limit of fixed character+fixed space. But maybe the “healing” might not be verydistracting.

> there is a reason why type designers make every character to be the same and try to balance everything including spacing.

But this was designed by type designers. So you can make exactly the same argument about texture healing.

Re: Monaspace

#179

Post by stevage »

chrismorgan wrote: post #88

If someone who maintains this site happens to be here: in the “code ligatures” section, where .overflow-y-scroll is used, that should be doing `overflow-y: auto` rather than `overflow-y: scroll`… though honestly I’m sceptical about the wisdom of the height capping anyway. `overflow: scroll` is almost never (p>0.999) the right thing, and users that don’t use overlay scrollbars are suffering because of the poor choice…

I have used it a few times in cases where I am showing some text whose size will vary a bit, around the scrolling threshold. Better to consistently show the scrollbar than have everything jump.

Still surprised that you are so worked up by this - is it really so common or so problematic?

Re: Monaspace

#180

Post by mzs »

inferiorhuman wrote: post #60
mzs wrote: 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…

Are you sure? On OSX they're showing up in Font Book under "Fixed Width" fonts. I'm using whatever version was released today, so that might be a recent fix.

Just checked, don't show-up in under fixed, monaspace 1.000 macos 13.6.1
Post reply on HN