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

131–140 of 206 posts

Re: Monaspace

#131

Post by philsnow »

flexagoon wrote: post #94
jeswin wrote: post #87

Earlier quoted context omitted.

GP asked for the opposite of that. Ligatures are troublesome while writing code.

Then you can enable the calt setting and disable all other ligatures

There are even checkboxes on the page to simultaneously disable ligatures and enable texture healing. They're just controlling whether various subfeatures of font-feature-settings are off/on.

I have a bunch of font-feature-settings subfeatures turned off explicitly in my userChrome.css, so it took me a little while to realize that that was what was messing with this site. I couldn't figure out what texture healing was supposed to do because toggling it wasn't helping, but it was because of my userChrome.

Re: Monaspace

#132

Post by pdpi »

sakjur wrote: post #104
nvartolomei wrote: post #18

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.

If this gets popular, I could see a text editor that lets you use a non-healing version of the font for any text that has been written in the viewport and then swaps it out as soon as you no longer looks at that block of text – or straight up uses a different font for my modifications compared to the committed code. But even without anything like that, if it’s good for reading I like to use different fonts when revie…

If it's good for reading, it's especially good for Github itself, which is a largely read-only interface for code.

Re: Monaspace

#133

Post by hutattedonmyarm »

lloeki wrote: post #122
hutattedonmyarm wrote: post #102

Looks kind of cool but I cannot stand their { and }. Otherwise I might give it a try

I find { to be ok, although I kinda expected them to differ across the font family (esp. Mechanical) The one that kills me is the squiggly comparisons ~>, I find it horrible and doesn't evoke the kind of comparison I see in Gemfiles. I read |> as "pipe + redirect" for me so turning them to triangles make them lose a ton of meaning. Oh and != is so much wider than >=, probably because == is, so as not to be confused w…

To be fair, ligatures are optional. I don’t like them either, but as long as I can turn it off I‘m ok

Re: Monaspace

#134

Post by eviks »

bsder wrote: post #25

Can we please stop with abusing ligatures for things like != into ≠? If you want APL, please use APL and leave the rest of us alone. != is two bloody characters not one . And now people are doing it for 3 characters. With this kind of thing, you get all the text editing idiocy of combining characters (like emojis) for no benefit at all. See: Text Editing Hates You Too https://lord.io/text-editing-hates-you-too/

That's use, not abuse, it's 2 chars, but 1 symbol, so it makes sense to use 1 symbol to represent it. That's the fundamental benefit - matching meaning to representation

Another way to fix the inconsistency is for the language designers to get unstuck from the past and allow literal ≠ in code

Re: Monaspace

#135

Post by omnimus »

lionkor wrote: post #114
zokier wrote: post #113

Earlier quoted context omitted.

So many people here are now praising texture healing, but to me its just half-way measure. Why are we as a community so resistant for adopting variable-width fonts? This texture healing already breaks perfect character cell grid, so in some ways it feels like worst of both worlds. I feel at least partially the same about fancy ligatures; we could just use the actual characters in source code, Unicode is widely suppor…

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.

Re: Monaspace

#137

Post by bool3max »

HellsMaddy wrote: post #84
helix278 wrote: 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 `…

Feels very hacky.

Re: Monaspace

#138

Post by eviks »

Cool new font features, though hopefully we get a chance to get proper proportional fonts insead of this hack in the next decade or two

Re: Monaspace

#139

Post by globular-toast »

I've tried many of the hip programming fonts but the one I keep coming back to is Ubuntu Mono. It's the only font that can give me a good density on my standard DPI screen. All the others seem to look like absolute crap when they are small and only look good when each character uses up about twice the pixels that I want it to.

Makes me wonder how other people deal with so few characters on their screen, or is everyone using high DPI, >1080p monitors?

I might try this one, but I doubt it will be any improvement.

Post reply on HN