diff options
| author | Daniel Mendler <mail@daniel-mendler.de> | 2022-02-09 11:09:29 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-09 11:09:29 +0100 |
| commit | c06bd574a8b0856c921feb96b2311627213cb7ef (patch) | |
| tree | af43eb93745e6546827f6903c04724dd31da26cc | |
| parent | dba8492f70a46fde51d6269ae971693fd1777575 (diff) | |
README: Fix typo
| -rw-r--r-- | README.org | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -184,7 +184,7 @@ 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~. 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~. +~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. |