Test: Terminal ligatures (stable)

[Tyriar]

Refs: #233006, #237492

• anyOS @ulugbekna
• anyOS @luabud

Complexity: 3

Create Issue

---

Terminal ligatures were tested last month but several important issues have been fixed and the feature declared stable. Here are the main changes, please test and verify them:

• terminal.integrated.fontLigatures changed to terminal.integrated.fontLigatures.enabled
• Ligatures should work mostly the same whether terminal.integrated.gpuAcceleration or "on" or "off"
• There's a new terminal.integrated.fontLigatures.featureSettings setting that allows configuring a font to use different ligature sets or character variants. I was testing this during development using Fira Code's stylistic sets
• There's a new terminal.integrated.fontLigatures.fallbackLigatures setting for fonts that aren't supported (no need to verify this)
• Ligatures should be temporarily disabled when either the selection or cursor is inside the ligature, this fixed the main 2 problems from last month.

[luabud]

LGTM. I wasn't able to get featureSettings to work but I also was not able to get editor.fontLigatures to work with the same value I was trying, so I think it may have been an issue with the font I am testing with.
The value I tried to configure was this:
"terminal.integrated.fontLigatures.featureSettings": "'ss19'",, based on microsoft/cascadia-code#407 (comment), as I wanted to swap the dotted zero with slash zero. But then "editor.fontLigatures": "'ssq19'", didn't do the trick for me on the editor either.
For that reason I didn't try filing an issue, but @Tyriar lmk if it's worth doing so.