search

githubnext / monaspace

An innovative superfamily of fonts for code
https://monaspace.githubnext.com
SIL Open Font License 1.1
13.18k stars 220 forks source link

Ability to prefer `!=` to `≠` #52

Open rainersigwald opened 8 months ago

rainersigwald commented 8 months ago

I know a lot of people really like ≠ as a replacement for !=, but I'm not among them. I was excited by the promise of turning off the ss01 stylistic set to avoid ≠, but it didn't work because (I think, based on the table on https://monaspace.githubnext.com/) it's also included in the dlig stylistic set, most of which I do want.

I think my ideal setup would be a way to opt into a space-adjusted glyph that's the inverse of the very nice =!, but out of ≠.

lonerabbits commented 7 months ago

According to my observation from the official website, the dlig set seem to be a collection of sets from ss01~ss08 and calt. It can also be seen that the number of sets in dlig is the sum of other sets.

So I set "editor.fontLigatures": "'ss02', 'ss03', 'ss04', 'ss05', 'ss06', 'ss07', 'ss08'" in VS Code and it seems to meet your needs.

Here, only the ss01 set which includes "!=" as "≠", and the dlig set which includes all sets, were removed.

I don’t know why this happens. It is consistent with the website but contradicts the README, which indicates "You must start the setting with 'calt', 'liga', 'dlig'".

In addition, I didn't observe the effects of two parameters calt and liga in VSC.

rainersigwald commented 7 months ago

So I set "editor.fontLigatures": "'ss02', 'ss03', 'ss04', 'ss05', 'ss06', 'ss07', 'ss08'" in VS Code and it seems to meet your needs.

This works for me too.

It is consistent with the website but contradicts the README, which indicates "You must start the setting with 'calt', 'liga', 'dlig'".

That is definitely what tripped me up!

I would still like an option for a != that is spaced more elegantly, but without dlig I'm much happier.