~pierrenn/ripgrep

d97e554a4e46855d0e6e8ab579359cc72cd245d1 — pierrenn 4 months ago fbc4f4b master readme_fix
update README
1 files changed, 2 insertions(+), 1 deletions(-)

M README.md
M README.md => README.md +2 -1
@@ 55,6 55,7 @@ $ rg --engine hyperscan -f myregexps my_file
```

Where `myregexps` is a compiled hyperscan DB or a list of regexps in the standard format or the hyperscan format, e.g.:

```
some default regexp
/some hyperscan regexp/imsHV8WcQ


@@ 72,7 73,7 @@ where `imsHV8WcQ` can be any subset of the following (case sensitive) option :
- 'C' : `HS_FLAG_COMBINATION`
- 'Q' : `HS_FLAG_QUIET`

We also provide options `--hyper--allow-empty`, `--hyper-utf8` and `--hyper-ucp` to override the value of each textual regular expression provided to the DB (ignored if you provide a compiled DB as we don't support DB edition). `caseless`, `multiline` and `dotall` default `ripgrep` options also override all regexps options (again, except when using a compiled hyperscan DB).
We also provide options `--hyper--allow-empty`, `--hyper-utf8` and `--hyper-ucp` to override the value of each textual regular expression provided to hyperscan (ignored if you provide a compiled DB as we don't support DB edition). `caseless`, `multiline` and `dotall` default `ripgrep` options also override all regexps options (again, except when using a compiled hyperscan DB).

Finally, you can also save a compiled database DB to your disk. This can be useful as sometimes most of the time spent by ripgrep is to compile the DB (on a single core).
Use the `-d/--hyper-write` parameter to save the DB to disk before starting the search :