LilyPond: fix wrong lexing of name containing builtin name#2071
Merged
jeanas merged 2 commits intopygments:masterfrom Mar 7, 2022
Merged
LilyPond: fix wrong lexing of name containing builtin name#2071jeanas merged 2 commits intopygments:masterfrom
jeanas merged 2 commits intopygments:masterfrom
Conversation
Non-builtin names were scanned character by character, possibly causing recognition of a suffix as builtin.
lemzwerg
reviewed
Feb 25, 2022
birkenfeld
reviewed
Mar 1, 2022
Contributor
Author
|
Apparently this was the 6000th commit in Pygments :) |
Member
|
Congrats! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Non-builtin names were scanned character by character, possibly
causing recognition of a suffix as builtin.