From 31acb66152f271357a54af47fcaa4b43f2c9220b Mon Sep 17 00:00:00 2001 From: Daniel Mendler Date: Mon, 22 Nov 2021 21:53:15 +0100 Subject: Update README --- README.org | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/README.org b/README.org index ce8ebdf..c9338e0 100644 --- a/README.org +++ b/README.org @@ -13,12 +13,18 @@ * Introduction Cape provides a bunch of Completion At Point Extensions which can be used in -combination with my [[https://github.com/minad/corfu][Corfu]] completion UI or the default completion UI. You can -register the ~cape-*-capf~ functions in the ~completion-at-point-functions~ list. -This makes the corresponding completion backends available to the -~completion-at-point~ command, which is usually invoked by pressing ~TAB~ or ~M-TAB~. -Furthermore there are a handful of dedicated completion commands ~cape-*~, which -you can bind directly to a key in your user configuration. +combination with my [[https://github.com/minad/corfu][Corfu]] completion UI or the default completion UI. The +completion backends used by ~completion-at-point~ are so called +~completion-at-point-functions~ (Capfs). + +You can register the ~cape-*-capf~ functions in the ~completion-at-point-functions~ +list. This makes the backends available for completion, which is usually invoked +by pressing ~TAB~ or ~M-TAB~. Furthermore there are a handful of dedicated +completion commands ~cape-*~, which you can bind directly to a key in your user +configuration. + +On the more experimental side, Cape provides the super power to transform +Company backends into Capfs and merge multiple Capfs into a Super-Capf! * Configuration -- cgit v1.0