summaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
authorDaniel Mendler <mail@daniel-mendler.de>2023-04-28 08:54:01 +0200
committerDaniel Mendler <mail@daniel-mendler.de>2023-04-28 08:54:01 +0200
commit06ade2c91d3127a7d57537488a28bf03fd2962ad (patch)
tree4d24d4445f15cca7737831cac2d1d51112175045 /README.org
parent33ab4c537144116e14e48e07fbbff9bd72b240b1 (diff)
Update README
Diffstat (limited to 'README.org')
-rw-r--r--README.org10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.org b/README.org
index 9424c8b..d851f64 100644
--- a/README.org
+++ b/README.org
@@ -20,11 +20,11 @@ concentrates on providing a polished completion UI. In-buffer completion UIs in
Emacs can hook into ~completion-in-region~, which implements the interaction with
the user. Completions at point are either provided by commands like
~dabbrev-completion~ or by pluggable backends (~completion-at-point-functions~,
-Capfs) and are then passed to ~completion-in-region~. Most programming language
-major modes implement a Capf. The Emacs language server clients use Capfs, which
-retrieve completions from the server via the language server protocol (LSP).
-Corfu does not include its own completion backends. The Emacs built-in Capfs and
-the Capfs provided by other programming language packages are usually
+Capfs) and are then passed to ~completion-in-region~. Most programming, text and
+shell major modes implement a Capf. The Emacs language server clients use Capfs,
+which retrieve completions from the server via the language server protocol
+(LSP). Corfu does not include its own completion backends. The Emacs built-in
+Capfs and the Capfs provided by other programming language packages are usually
sufficient. A few additional Capfs and completion utilities are provided by the
[[https://github.com/minad/cape][Cape]] package.