diff options
| -rw-r--r-- | README.org | 21 | ||||
| -rw-r--r-- | images/describe-function-eis-ff.png | bin | 0 -> 132267 bytes |
2 files changed, 21 insertions, 0 deletions
@@ -41,6 +41,16 @@ the candidates displayed vertically, you can use [[https://github.com/oantolin/i Bug reports are highly welcome and appreciated! +* Screenshot + +This is what it looks like to use =describe-function= (bound by default +to =C-h f=) to match =eis ff=. Notice that in this particular case =eis= +matched as an initialism, and =ff= matched as a regexp. The completion +UI in the screenshot is [[https://github.com/oantolin/icomplete-vertical][icomplete-vertical]] and the theme is +Protesilaos Stavrou's lovely [[https://gitlab.com/protesilaos/modus-themes][modus-operandi]]. + +[[images/describe-function-eis-ff.png]] + * Customization ** Component matching styles @@ -156,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=.) diff --git a/images/describe-function-eis-ff.png b/images/describe-function-eis-ff.png Binary files differnew file mode 100644 index 0000000..87d2467 --- /dev/null +++ b/images/describe-function-eis-ff.png |
