summaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
Diffstat (limited to 'README.org')
-rw-r--r--README.org21
1 files changed, 0 insertions, 21 deletions
diff --git a/README.org b/README.org
index 82605da..dea6d1f 100644
--- a/README.org
+++ b/README.org
@@ -194,27 +194,6 @@ achieve a similarly refreshing strategy.
(list (cape-capf-buster #'some-caching-capf)))
#+end_src
-** Repair misbehaving Capfs
-
-/Sweep misbehaving Capfs under the Cape!/
-
-Unfortunately some completion of point functions from Emacs show misbehavior.
-This is not a term I've made up, but minibuffer.el distinguishes old-style
-("misbehaving") Capfs and modern-style Capfs. The misbehaving Capfs do not
-return a completion table but just perform completion right away. Such behavior
-is particularily harmful for completion UIs like Company or Corfu in
-idle/auto-completion mode. There is at least one completion function, which
-affects shell completions: ~pcomplete-completions-at-point~.
-
-#+begin_src emacs-lisp
- (advice-add 'pcomplete-completions-at-point :around #'cape-repair-misbehaving-capf)
-#+end_src
-
-By wrapping it with ~cape-repair-misbehaving-capf~ we can repair the occasional
-misbehavior of the Capf. In the long term the underlying issue should of course
-be fixed in ~pcomplete-completions-at-point~ but in the meantime we can live with
-a localized fix.
-
** Other Capf transformers
- ~cape-silent-capf~: Wrap a chatty Capf and silence it.