mirror of
https://github.com/BurntSushi/ripgrep.git
synced 2025-03-17 20:28:03 +02:00
doc: improve PCRE2 failure mode documentation
If a user tries to search for an explicit `\n` character in a PCRE2 regex, ripgrep won't report an error and instead will (likely) silently fail to match. Fixes #1261
This commit is contained in:
parent
9268ff8e8d
commit
01e8e11621
@ -1995,7 +1995,12 @@ or backreferences.
|
||||
|
||||
Note that PCRE2 is an optional ripgrep feature. If PCRE2 wasn't included in
|
||||
your build of ripgrep, then using this flag will result in ripgrep printing
|
||||
an error message and exiting.
|
||||
an error message and exiting. PCRE2 may also have worse user experience in
|
||||
some cases, since it has fewer introspection APIs than ripgrep's default regex
|
||||
engine. For example, if you use a '\n' in a PCRE2 regex without the
|
||||
'-U/--multiline' flag, then ripgrep will silently fail to match anything
|
||||
instead of reporting an error immediately (like it does with the default
|
||||
regex engine).
|
||||
|
||||
Related flags: --no-pcre2-unicode
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user