-
Notifications
You must be signed in to change notification settings - Fork 5
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
tmbundle: Make tmLanguage compatible with PCRE2 #19
Comments
17 tasks
Will look shortly. Thanks for the report! |
No. GitHub uses PCRE for grammar parsing for performance reasons. |
mlrawlings
changed the title
Make tmLanguage compatible with PCRE2
tmbundle: Make tmLanguage compatible with PCRE2
Feb 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
👋 I'm the lead maintainer of the https://github.com/github/linguist library which is used for language detection and providing the syntax highlighting for languages on GitHub.com, and we use this grammar.
Our grammar compiler has found several problems with your grammar which I thought I'd let you know about.
These regexes have quite a few problems as you can see in the regex101 link after each:
marko-tmbundle/syntaxes/marko.tmLanguage.json
Line 779 in 60ded48
https://regex101.com/r/pSG73T/1
marko-tmbundle/syntaxes/marko.tmLanguage.json
Line 108 in 60ded48
... and repeated again at:
marko-tmbundle/syntaxes/marko.tmLanguage.json
Line 130 in 60ded48
https://regex101.com/r/NlVs41/1
These are the errors our compiler reported:
text.marko
(insyntaxes/marko.tmLanguage.json
) contains a malformed regex (regex "(?=[,;\](]|/>|(?<=[^=])>|(?<!(?:
...": nothing to repeat (at offset 105))text.marko
(insyntaxes/marko.tmLanguage.json
) contains a malformed regex (regex "(?=[,;\]]|/>|(?<=[^=])>|(?<!(?:^
...": nothing to repeat (at offset 104))text.marko
(insyntaxes/marko.tmLanguage.json
) contains a malformed regex (regex "(?=[,;\]]|/>|(?<=[^=])>|(?<!(?:^
...": nothing to repeat (at offset 104))The text was updated successfully, but these errors were encountered: