Support for ligatures in JavaScript?
See original GitHub issueHi, I see that if I write =>
it gets converted in:
<span class="token operator">=</span>
<span class="token operator">></span>
But this breaks the ligature of the font I’m using (Fira Code).
Could it be possible to group together tokens of the same type to allow ligatures? Ideally the markup should be:
<span class="token operator">=></span>
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
font-variant-ligatures - CSS: Cascading Style Sheets | MDN
The font-variant-ligatures CSS property controls which ligatures and contextual forms are used in textual content of the elements it applies ...
Read more >Detecting Ligature Icons With JavaScript - Steven Lambert
A deep dive into detecting when a string of text has been replaced with a ligature icon.
Read more >Enable Font Ligatures in VS Code - World of Zero
Some free fonts that support ligatures are: ... To enable font ligatures in Visual Studio Code you will need to edit the settings.json...
Read more >Ligatures in CSS3 @font-face - Stack Overflow
There is probably no JavaScript-based way to overcome this. Replacing character sequences by ligature characters is possible of course, ...
Read more >font-ligatures - npm
Find ligature replacements for any system font. Latest version: 1.4.1, last published: a year ago. Start using font-ligatures in your ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@RunDevelopment Nice… the documentation actually has a complete table of all operators, https://doc.rust-lang.org/book/appendix-02-operators.html
Thanks for reporting. This should be fixed now.