Open MrScottyTay opened 8 months ago
[EDITED to add: several people suggested "editor.fontFamily": "Monaspace Argon Var"
and this has improved things me, along with restarting VS Code]
Can confirm the ligatures are not working for me in VS Code on Windows 11. I used the suggested setting:
"editor.fontFamily": "Monaspace",
"editor.fontLigatures": "'ss01', 'ss02', 'ss03', 'ss04', 'ss05', 'ss06', 'ss07', 'ss08', 'calt', 'dlig'",
And I'm getting an unwanted ligature for fi
but not for coding ligatures such as !=
.
All the coding ligatures are working for me using Fira Code, but not Monaspace.
Similarly, I am unable to get ligatures working in Jetbrains Rider. Looks like the Enable ligatures
setting only enables texture healing, but doesn't affect code ligatures.
The README seems to indicate this: https://github.com/githubnext/monaspace#editors
The README seems to indicate this: https://github.com/githubnext/monaspace#editors
❔
Visual Studio enables* ligatures by default, you can't turn them off. You just need to select the font and restart VS (ligatures won't work before restarting)
The texture healing seems to work for me (using the variable fonts), you can compare a standalone 'm' to 'imi' to see if it works. Currently enabling ligatures doesn't seem to enable code ligatures, but that's an issue not limited to VS.
@dominicsayers Visual Studio Code is quite different from Visual Studio
I don't think there a variant called "Monaspace", you need to select a specific variant.
I'm using the variable variant of argon, so:
"editor.fontFamily": "Monaspace Argon Var",
Selecting the specific stylistic sets then enables the respective ligatures, at least on my machine, despite simply enabling ligature not doing that.
I agree that using "editor.fontFamily": "Monaspace Argon Var"
improves the situation. It's worth saying the current documentation is silent on this point and could be improved.
I too am having issues with ligatures in Visual Studio in Windows 11. Have installed the fonts, selected Monaspace Neon Var
, and restarted Visual Studio. Texture healing seems to be working, but I'm not seeing any ligatures.
Ligatures do seem to work fine with FiraCode in Visual Studio, and in VSCode with the Monaspace fonts.
One thing to note- the Monaspace fonts are not showing up as monospace in Visual Studio (which bolds monospace fonts in the list). Not sure if I botched the install or this is intended.
I've been fiddling around and, following the README instructions I finally got coding ligatures to work by using these settings :
"editor.fontFamily": "Monaspace Krypton",
"editor.fontLigatures": "'calt', 'liga', 'dlig'",
Using "editor.fontLigatures": true,
wouldn't work for me using either the variable or normal font.
Can confirm @Aurel-Cros solution also worked for VSCode running on Ubuntu 22.04
"editor.fontFamily": "'Monaspace Neon', monospace",
"editor.fontLigatures": "'calt', 'liga', 'dlig'",
Worth noting that the fonts and ligatures worked without a hitch on Jetbrain's IDEs.
This seems to be a solution for VSCode and that's ok, but what about Visual Studio (not Code)? Ligatures are not working for me either
I've been fiddling around and, following the README instructions I finally got coding ligatures to work by using these settings :
"editor.fontFamily": "Monaspace Krypton", "editor.fontLigatures": "'calt', 'liga', 'dlig'",
Using
"editor.fontLigatures": true,
wouldn't work for me using either the variable or normal font.
Just adding my +1 here - I really like how monaspace neon looks, but ligatures do not work on Visual Studio (not vs code!).
The texture healing feature works well, however.
Basically the title, I know this is probably more of a Visual Studio question but since it pertains specifically to this project, especially texture healing I thought it would be best to just ask here.