From 180054d7dc6975a8eb76e9020b00bfcbea9edf3a Mon Sep 17 00:00:00 2001 From: Andrew Gallant Date: Mon, 20 Aug 2018 17:58:29 -0400 Subject: doc: caveats --- FAQ.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'FAQ.md') diff --git a/FAQ.md b/FAQ.md index 9a803176..6a301d00 100644 --- a/FAQ.md +++ b/FAQ.md @@ -675,14 +675,18 @@ no longer needs to do any kind of UTF-8 checks. This allows the file to get memory mapped and passed right through PCRE2's JIT at impressive speeds. (As a brief and interesting historical note, the configuration of "memory map + multiline + no-Unicode" is exactly the configuration used by The Silver -Searcher. This analysis perhaps sheds some reasoning as to why it converged on -that specific setting!) +Searcher. This analysis perhaps sheds some reasoning as to why that +configuration is useful!) In summary, if you want PCRE2 to go as fast as possible and you don't care about Unicode and you don't care about matches possibly spanning across multiple lines, then enable multiline mode with `-U` and disable PCRE2's Unicode support with the `--no-pcre2-unicode` flag. +Caveat emptor: This author is not a PCRE2 exit, so there may be APIs that can +improve performance. Similarly, there may be alternative designs for a +searching tool that are more amenable to how PCRE2 works. +

When I run rg, why does it execute some other command? -- cgit v1.2.3