Skip to content

Ligature support #216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kamek-pf opened this issue Oct 12, 2017 · 3 comments · Fixed by #217
Closed

Ligature support #216

kamek-pf opened this issue Oct 12, 2017 · 3 comments · Fixed by #217

Comments

@kamek-pf
Copy link

Sublime added ligature support in build 3146.
Using FiraCode, here's what happens in Rust sources :
ss

Ligatures work fine in other languages, and as someone pointed out in this discussion, we might want to look into the syntax definition itself.

Sublime Text Version

Sublime Text 3 (Build 3147)

Rust Enhanced Version

v2.2.0

Operating system

Arch

Expected behavior

Ligatures should work everywhere

Actual behavior

Some ligatures aren't applied

@dten
Copy link

dten commented Oct 12, 2017

Looks like the pattwrn below would match the ! separately from the =

   - match: '\.\.\.|\.\.||[-=<>&|!~@?+*/%^''#$]|\b_\b'
      scope: keyword.operator.rust

I can sort it but i can't even figure out how to show ligatures 😅

@kamek-pf
Copy link
Author

I didn't do anything special to make them work, they just showed up after the upgrade.
Make sure your build is 3146 or newer and use a font that support ligatures '_'

3146 is in the dev branch btw, stable is stuck at 3143

@dten
Copy link

dten commented Oct 12, 2017

manged to enable FiraCode and fixed it, PR pending
#217

hmm it's made expand selection a bit odd, investigating
edit: sorted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants