Ripgrep doesn`t always support PCRE2

[pechorin]

Ripgrep doesn`t always support PCRE2

[wookayin]

For future reference:

This often happens when one mistakenly have rg installed in their anaconda environments, which often supersedes in PATH. The official prebuilt binaries well support PCRE2.

[BurntSushi]

If you're installing ripgrep with Cargo, you should be able to enable PCRE2 support via cargo install ripgrep --features pcre2.

Also, you all might consider using --auto-hybrid-regex. I don't know exactly how you're invoking ripgrep and what kind of regexes you're using, but enabling PCRE2 can be slower: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#pcre2-slow (There are ways to make it faster, which the FAQ entry addresses.) However, if you use --auto-hybrid-regex, then ripgrep will automatically use its default engine if it can (when the regex doesn't have look-around or backreferences).

[pechorin]

Hello, thanks for report. I will try to add PCRE2 check for better error message :)

Also i think too many any-jump regexps uses PCRE2, so this is not in my road-map, but i think i will research this problem.

[AZanellato]

Not only that. The installation through cargo doesn't support PCRE2 by default.

[pechorin]

Okay, not all regexp rules uses PCRE2 look-ahed/behind so i think i can enable --auto-hybrid-regex instead of strict --PCRE2

be4b64a

Please try and let me know if it helps :)

[AZanellato]

Thank you @pechorin and @BurntSushi !