summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Mendler <mail@daniel-mendler.de>2021-03-23 19:53:04 +0100
committerDaniel Mendler <mail@daniel-mendler.de>2021-03-23 19:53:04 +0100
commite5cb3f7b57d910247d7551866560dfac3ca07cdb (patch)
tree5abbe7377f2f85b43fa7e224913b8271bd98bf48
parentf6394f19f3993831dadd91046090d7a2498facca (diff)
update readme
-rw-r--r--README.org10
1 files changed, 3 insertions, 7 deletions
diff --git a/README.org b/README.org
index 5d809d3..e0680a9 100644
--- a/README.org
+++ b/README.org
@@ -100,11 +100,8 @@ define new matching styles. The predefined ones are:
- orderless-regexp :: the component is treated as a regexp that must
match somewhere in the candidate.
- If the component is not a valid regexp, it matches literally.
- (Having the component be invalid is actually pretty common while you
- are typing, so be prepared for the results to be a little funny
- before you close a bracket or parentheses, etc.)
-
+ If the component is not a valid regexp, it is ignored.
+
- orderless-literal :: the component is treated as a literal string
that must occur in the candidate.
@@ -117,7 +114,7 @@ define new matching styles. The predefined ones are:
probably don't want to use this style directly in
=orderless-matching-styles= but with a style dispatcher instead. There
is an example in the section on style dispatchers.
-
+
- orderless-prefixes :: the component is split at word endings and
each piece must match at a word boundary in the candidate, occurring
in that order.
@@ -406,4 +403,3 @@ you get out of order matching!
- Ivy has =ivy-restrict-to-matches=, bound to =S-SPC=, so you can get the
effect of out of order matching without using =ivy--regex-ignore-order=.
-