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

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

[elpa] externals/corfu 0e84897: README: Remove multi-capf backend idea


From: ELPA Syncer
Subject: [elpa] externals/corfu 0e84897: README: Remove multi-capf backend idea
Date: Sat, 17 Jul 2021 19:57:06 -0400 (EDT)

branch: externals/corfu
commit 0e8489751acc9c28ec2e6c1218ef4202dc6c6eff
Author: Daniel Mendler <mail@daniel-mendler.de>
Commit: Daniel Mendler <mail@daniel-mendler.de>

    README: Remove multi-capf backend idea
    
    It turns out the comint completion backend supports additional file 
completions
    (See #9).
---
 README.org | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/README.org b/README.org
index dfd3e15..eea3657 100644
--- a/README.org
+++ b/README.org
@@ -34,9 +34,9 @@
 
 * Features
 
-  - Timer-based auto-completions (off by default, set ~corfu-auto~)
+  - Timer-based auto-completions (/off/ by default, set ~corfu-auto~)
   - Popup display with scrollbar indicator and arrow key navigation
-  - The popup must be summoned explicitly by pressing =TAB=
+  - In manual mode, the popup must be summoned explicitly by pressing =TAB=
   - The current candidate is inserted with =TAB= and selected with =RET=
   - Candidates sorting by prefix, string length and alphabetically
   - Completion is automatically terminated after candidate selection
@@ -143,15 +143,14 @@
 
 * Caveats
 
-  Corfu works in most scenarios. However there are a few known technical 
caveats.
+  Corfu works well in most scenarios. However there are a few known technical
+  caveats.
 
   - Corfu falls back to the default Completion buffer on non-graphical 
displays,
     since Corfu requires child frames.
   - The abort handling could be improved, for example the input could be 
undone.
   - Company kind icons, docsig and match data are not supported
     (~company-kind~, ~company-docsig~, ~company-match~).
-  - No support for multi-backends like Company. A possible multi-capf backend
-    could be implemented.
   - No sorting by history, since ~completion-at-point~ does not
     maintain a history (See branch =history= for a possible solution).
 



reply via email to

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