summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOmar Antolín <omar.antolin@gmail.com>2020-04-23 12:33:29 -0500
committerOmar Antolín <omar.antolin@gmail.com>2020-04-23 12:33:29 -0500
commitf2af44bf2e5ca7a0bb6bb12677e9919b33216848 (patch)
tree09b711db2d7b7d18e90ce556a9b9f6fa297e89c6
parent3827b4119c6b50edd036b540635cca0f310a0518 (diff)
Mention Icicles's progressive matching
-rw-r--r--README.org11
1 files changed, 11 insertions, 0 deletions
diff --git a/README.org b/README.org
index 1047986..22de6fe 100644
--- a/README.org
+++ b/README.org
@@ -166,3 +166,14 @@ The components can be matched literally, as regexps, as initialisms or
in the flex style (called "fuzzy" in prescient). In addition to
matching, =prescient.el= also supports sorting of candidates (=orderless=
leaves that up to the candidate source and the completion UI).
+
+* Icicles's progressive matching
+
+An effect equivalent to matching multiple components in any order can
+be achieved in completion frameworks that provide a way to restrict
+further matching to the current lists of candidates. In [[https://www.emacswiki.org/emacs/Icicles][Icicles]] this
+is called /progressive completion/ and using =S-SPC= instead of =SPC= to
+separate components will do it. (Note that Ivy has an analogous
+command, also bound to =S-SPC=, called =ivy-restrict-to-matches=, so you
+can get the effect of out of order matching without using
+=ivy--regex-ignore-order=.)