zlacker

>>davidb+(OP)
It's a shame that on VS Code at least (I'm not sure if this applies in other contexts), the "textual healing" feature goes hand-in-hand with ligatures. There is no way to enable textual healing if you prefer not to use programming ligatures.

>>SteveP+MY
From https://github.com/githubnext/monaspace?tab=readme-ov-file#v...

> If you want coding ligatures but do not want texture healing, you can elide the calt setting:

>>matthe+S11
GP asked for the opposite of that. Ligatures are troublesome while writing code.

>>jeswin+sc1
Then you can enable the calt setting and disable all other ligatures

>>flexag+If1
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.