emacs-elpa-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[elpa] externals/cape 3495692f4c 133/146: Expand README


From: ELPA Syncer
Subject: [elpa] externals/cape 3495692f4c 133/146: Expand README
Date: Sun, 9 Jan 2022 20:57:49 -0500 (EST)

branch: externals/cape
commit 3495692f4c5657496e51a3de840fee6de54aa726
Author: Daniel Mendler <mail@daniel-mendler.de>
Commit: Daniel Mendler <mail@daniel-mendler.de>

    Expand README
---
 README.org | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/README.org b/README.org
index 89847b98c9..82605da70b 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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]