summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Mendler <mail@daniel-mendler.de>2021-12-12 23:53:48 +0100
committerDaniel Mendler <mail@daniel-mendler.de>2021-12-12 23:53:48 +0100
commit3495692f4c5657496e51a3de840fee6de54aa726 (patch)
tree1a0944c65329ec0f350faf1d6d522df7e2fb22ad
parentc442f055dd662b165e8a9a3fb503c8e9a29c1b58 (diff)
Expand README
-rw-r--r--README.org7
1 files changed, 6 insertions, 1 deletions
diff --git a/README.org b/README.org
index 89847b9..82605da 100644
--- a/README.org
+++ b/README.org
@@ -204,12 +204,17 @@ This is not a term I've made up, but minibuffer.el distinguishes old-style
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 the Eshell:
+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.