branch: externals/cape
commit e01162ab1007457aba788916c1d59de8d6083b25
Author: Daniel Mendler <m...@daniel-mendler.de>
Commit: Daniel Mendler <m...@daniel-mendler.de>
README: Expand on restrictions of cape-super-capf
---
README.org | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/README.org b/README.org
index cf8ef729e1..5167dd882a 100644
--- a/README.org
+++ b/README.org
@@ -182,7 +182,9 @@ combine multiple Capfs, such that the candidates from
multiple sources appear
Completion table merging works only for tables which are sufficiently
well-behaved and tables which do not define completion boundaries.
~cape-super-capf~ has the same restrictions as ~completion-table-merge~ and
-~completion-table-in-turn~.
+~completion-table-in-turn~. As a simple rule of thumb, ~cape-super-capf~ works
only
+well for static completion functions like ~cape-dabbrev~, ~cape-keyword~,
+~cape-ispell,~ etc., but not for complex multi-step completions like
~cape-file~.
#+begin_src emacs-lisp
;; Merge the dabbrev, dict and keyword capfs, display candidates together.
