diff options
| author | Canop <cano.petrole@gmail.com> | 2020-06-20 20:48:28 +0200 |
|---|---|---|
| committer | Canop <cano.petrole@gmail.com> | 2020-06-20 20:48:28 +0200 |
| commit | 0785091302b6118c19f2a6537f7a7337745af0b2 (patch) | |
| tree | 871ac632c21ddaf977c593d386e5c2eb926f310b /website/docs/input.md | |
| parent | 249bbd42bcf6df8351c0929c7e749bab9ef148ad (diff) | |
version 0.16.0 - pattern compositionv0.16.0
Diffstat (limited to 'website/docs/input.md')
| -rw-r--r-- | website/docs/input.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/website/docs/input.md b/website/docs/input.md index e0990fc..89a3cfd 100644 --- a/website/docs/input.md +++ b/website/docs/input.md @@ -50,8 +50,8 @@ The caracters you use as operators and the parenthesis can be useful in patterns Most often you'll just type what feels natural and broot will select the interpretation which makes sense but you might be interested in a few rules: -* parenthesis and operators in the second pattern part (parts being separated by `/`) are part of the patternC, which explains why `/(json|xml)` is interpreted as a regular expression. If you want to do a fuzzy search for a `|` in the name of your files, you'll need to have an explicit pattern mode : `nf/a|b` because `a|b` would search for files whose name contains either `a` or `b`. And to ensure an operator or closing parenthesis isn't interpreted as part of your pattern, just close it with a `/`. -* broot interprets the left operand before the right one and don't interpret the second one if it looks useless. So if you want to search your whole disk for json files containing `abcd`, it will be faster to use `/json$/&c/abcd` rather than `c/abcd/&/json$/` which would look at the file name only after having scanned the content. +* parenthesis and operators in the second pattern part (parts being separated by `/`) are part of the pattern, which explains why `/(json|xml)` is interpreted as a regular expression. If you want to do a fuzzy search for a `|` in the name of your files, you'll need to have an explicit pattern mode : `nf/a|b` because `a|b` would search for files whose name contains either `a` or `b`. And to ensure an operator or closing parenthesis isn't interpreted as part of your pattern, just close it with a `/`. +* broot interprets the left operand before the right one and doesn't interpret the second one if it's not necessary. So if you want to search your whole disk for json files containing `abcd`, it will be faster to use `/json$/&c/abcd` rather than `c/abcd/&/json$/` which would look at the file name only after having scanned the content. ## The verb invocation |