From 7a547b5722190429f9ac6b3417d615af63a58865 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Omar=20Antol=C3=ADn=20Camarena?= Date: Mon, 27 Apr 2020 23:13:10 -0500 Subject: Drew says "progressive completion" --- README.org | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.org b/README.org index 6b60ec7..0c510ac 100644 --- a/README.org +++ b/README.org @@ -60,7 +60,7 @@ Bug reports are highly welcome and appreciated! - [[#related-packages][Related packages]] - [[#ivy-and-helm][Ivy and Helm]] - [[#prescient][Prescient]] - - [[#icicless-progressive-matching][Icicles's progressive matching]] + - [[#icicless-progressive-completion][Icicles's progressive completion]] - [[#integration-with-other-completion-uis][Integration with other completion UIs]] - [[#ivy][Ivy]] - [[#selectrum][Selectrum]] @@ -209,7 +209,7 @@ 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 +** Icicles's progressive completion An effect equivalent to matching multiple components in any order can be achieved in completion frameworks that provide a way to restrict -- cgit v1.0