We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[.][^.]*$
Hi,
pcre2 incorrectly parses [.][^.]*$.
When I use ag, which uses pcre2, vs ripgrep, which uses rust's implementation of regexp, I get:
fragmede@samairmac:~/projects/ag_bug$ find . | ag -o [.][^.]*$ | sort -u | tail -3 ./the_silver_searcher/tests/word_regexp.t ./the_silver_searcher/the_silver_searcher.spec ./the_silver_searcher/the_silver_searcher.spec.in fragmede@samairmac:~/projects/ag_bug$ find . | rg -o [.][^.]*$ | sort -u | tail -3 .w32 .yml .zig fragmede@samairmac:~/projects/ag_bug$
The text was updated successfully, but these errors were encountered:
Looks like it could be an ag bug? If you tell ripgrep to use PCRE2, then it gets the same result:
ag
$ git remote -v origin [email protected]:ggreer/the_silver_searcher (fetch) origin [email protected]:ggreer/the_silver_searcher (push) $ git rev-parse HEAD a61f1780b64266587e7bc30f0f5f71c6cca97c0f $ find . | rg -P -o [.][^.]*$ | sort -u | tail -3 .txt .w32 .yml
Note also that ag uses PCRE, not PCRE2. ripgrep uses PCRE2.
Sorry, something went wrong.
Ah thanks. Got confused tracking down dependencies. I'll file it with ag directly.
Closing this issue as not a bug.
No branches or pull requests
Hi,
pcre2 incorrectly parses
[.][^.]*$
.When I use ag, which uses pcre2, vs ripgrep, which uses rust's implementation of regexp, I get:
The text was updated successfully, but these errors were encountered: