diff options
| author | Daniel Mendler <mail@daniel-mendler.de> | 2022-01-19 23:50:06 +0100 |
|---|---|---|
| committer | Daniel Mendler <mail@daniel-mendler.de> | 2022-01-19 23:50:06 +0100 |
| commit | e01162ab1007457aba788916c1d59de8d6083b25 (patch) | |
| tree | e20721ccfcbe2217d0ba33f7660b755c4f5dcb6a | |
| parent | a57cc31f42a86cdaaee027daafad814a08ffbdcc (diff) | |
README: Expand on restrictions of cape-super-capf
| -rw-r--r-- | README.org | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -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. |