VS Code users can't tune ligatures by font or code context
Some VS Code developers want to pair the letterforms of one font with programming ligatures from another, or disable ligatures only in contexts such as strings. The reports describe global or language-level settings as too blunt, leaving users to turn ligatures off or rely on a custom CSS workaround. The evidence is limited to VS Code requests from 2017–2020, so current demand and editor behavior should be rechecked.
For VS Code developers who customize editor typography. Mentioned from Jul 2017 to Nov 2020 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 1.0/10
- Pain
- 4.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Low
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
For example, I would really like to use Operator Mono letters together with Fira Code ligatures. Atom-editor lets you do this. A hacky workaround is with the Custom CSS and JS Loader extension
Font ligatures look bad in PHP. The solution I came to was turning off font ligatures for PHP only in settings.json:
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks