summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorJunegunn Choi <junegunn.c@gmail.com>2024-08-16 18:20:55 +0900
committerJunegunn Choi <junegunn.c@gmail.com>2024-08-29 17:08:23 +0900
commitc0f27751d378b0be0aeb0572dbeaac24153a3137 (patch)
tree2e023051ac1ce9767145ab487bb41420cd92ba8b /man
parentefbcd5a6833939c3e9c1347587fd5118e8f3705e (diff)
downloadfzf-c0f27751d378b0be0aeb0572dbeaac24153a3137.tar.gz
Add exact-boundary-match to man page
Diffstat (limited to 'man')
-rw-r--r--man/man1/fzf.116
1 files changed, 16 insertions, 0 deletions
diff --git a/man/man1/fzf.1 b/man/man1/fzf.1
index 811de487..f8774760 100644
--- a/man/man1/fzf.1
+++ b/man/man1/fzf.1
@@ -1146,6 +1146,22 @@ A term can be prefixed by \fB^\fR, or suffixed by \fB$\fR to become an
anchored-match term. Then fzf will search for the lines that start with or end
with the given string. An anchored-match term is also an exact-match term.
+.SS Exact\-boundary\-match (quoted both ends)
+A single-quoted term is interpreted as an "exact\-boundary\-match". fzf will
+search for the exact occurrences of the string with both ends at the word
+boundaries. Unlike in regular expressions, this also sees an underscore as
+a word boundary. But the words around underscores are ranked lower and appear
+later in the result than the other words around the other types of word
+boundaries.
+
+1. xxx foo xxx (highest score)
+.br
+2. xxx foo_xxx
+.br
+3. xxx_foo xxx
+.br
+4. xxx_foo_xxx (lowest score)
+
.SS Negation
If a term is prefixed by \fB!\fR, fzf will exclude the lines that satisfy the
term from the result. In this case, fzf performs exact match by default.