branch: externals/corfu
commit 5641e3bf80bb2b24da83fec49fc44c69169e1bcb
Author: Daniel Mendler <[email protected]>
Commit: Daniel Mendler <[email protected]>
Update readme
---
README.org | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/README.org b/README.org
index b8205f2..326dec1 100644
--- a/README.org
+++ b/README.org
@@ -20,12 +20,13 @@ two distinct use cases, also leading to code bases which
are easier to
understand.
Corfu is a minimal package (~500 lines of code without whitespace and
comments).
-In contrast to the featureful and complex Company package, Corfu only offers a
-completion UI and does not include custom completion backends. Completions are
-generated by calling the ~completion-at-point-functions~ (Capfs). Many code
-completion backends provide such a Capf, such that relying only on the default
-completion is often sufficient. For example the language server packages,
[[https://github.com/joaotavora/eglot][Eglot]]
-and [[https://github.com/emacs-lsp/lsp-mode][Lsp-mode]], both implement a Capf.
+In contrast to the featureful and complex Company package, Corfu concentrates
on
+the completion UI and does not include custom completion backends. Completions
+are either provided by commands like ~dabbrev-completion~ or by pluggable
+backends (~completion-at-point-functions~, Capfs). Many programming language
+major modes implement a Capf. Furthermore the language server packages,
[[https://github.com/joaotavora/eglot][Eglot]]
+and [[https://github.com/emacs-lsp/lsp-mode][Lsp-mode]], both use Capfs which
talk to the LSP server to retrieve the
+completions.
[[https://github.com/minad/corfu/blob/main/screenshot.png?raw=true]]
