Skip to content
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

[Markdown] Fix more arrow like ligatures #2449

Merged
merged 1 commit into from
Aug 18, 2020

Conversation

deathaxe
Copy link
Collaborator

Addresses MonoLisaFont/feedback#36

This PR extends the existing ligatures tokenization fix to match more arrow like ligatures correctly, by just consuming everything, which looks like a ligature candidate.

Addresses MonoLisaFont/feedback#36

This commit extends the existing ligatures tokenization fix to match
more arrow like ligatures correctly, by just consuming everything, which
looks like a ligature candidate.
@deathaxe deathaxe force-pushed the pr/markdown/fix-ligatures branch from e8a73d0 to d306a03 Compare August 16, 2020 13:31
@wbond wbond merged commit b8836b4 into sublimehq:master Aug 18, 2020
@deathaxe deathaxe deleted the pr/markdown/fix-ligatures branch August 18, 2020 15:47
charlievieth pushed a commit to charlievieth/Packages that referenced this pull request Aug 25, 2020
Addresses MonoLisaFont/feedback#36

This commit extends the existing ligatures tokenization fix to match
more arrow like ligatures correctly, by just consuming everything, which
looks like a ligature candidate.
deathaxe added a commit to deathaxe/sublime-packages that referenced this pull request Jul 25, 2021
Addresses MonoLisaFont/feedback#36

This commit extends the existing ligatures tokenization fix to match
more arrow like ligatures correctly, by just consuming everything, which
looks like a ligature candidate.
mitranim pushed a commit to mitranim/Packages that referenced this pull request Mar 25, 2022
Addresses MonoLisaFont/feedback#36

This commit extends the existing ligatures tokenization fix to match
more arrow like ligatures correctly, by just consuming everything, which
looks like a ligature candidate.
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 this pull request may close these issues.

3 participants