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

invalid backref number #10

Open
zoli opened this issue Jul 27, 2016 · 1 comment
Open

invalid backref number #10

zoli opened this issue Jul 27, 2016 · 1 comment
Labels

Comments

@zoli
Copy link
Member

zoli commented Jul 27, 2016

Some tmLanguage files have patterns with begin and end, If the end regex has backrefer number like this It raises invalid backref number error because we aren't relating begin and end regex on compiling.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36385265-invalid-backref-number?utm_campaign=plugin&utm_content=tracker%2F35047411&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F35047411&utm_medium=issues&utm_source=github).
@zoli zoli added the bug label Jul 27, 2016
@zoli zoli added this to the v0.1 milestone Jul 27, 2016
@zoli zoli mentioned this issue Jul 27, 2016
14 tasks
@ricochet1k
Copy link
Member

Depends on exactly how the parser works, but it seems to me that replacing the backreferences by an escaped version of the match in the beginning might be the best way to do it. Compiling different regexes for each match is kinda annoying though.

@zoli zoli removed this from the v0.1 milestone Dec 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants