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

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

[elpa] externals/cape ceca3a3d06 077/146: Expand readme


From: ELPA Syncer
Subject: [elpa] externals/cape ceca3a3d06 077/146: Expand readme
Date: Sun, 9 Jan 2022 20:57:44 -0500 (EST)

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

    Expand readme
---
 README.org | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README.org b/README.org
index 509dfffb7e..ea7a624e04 100644
--- a/README.org
+++ b/README.org
@@ -22,7 +22,10 @@ You can register the ~cape-*~ functions in the 
~completion-at-point-functions~ l
 This makes the backends available for completion, which is usually invoked by
 pressing ~TAB~ or ~M-TAB~. The functions can also be invoked interactively to
 trigger the respective completion at point. You can bind them directly to a key
-in your user configuration.
+in your user configuration. Notable commands/capfs are ~cape-line~ for 
completion
+of a line from the current buffer and ~cape-file~ for completion of a file 
name.
+The command ~cape-symbol~ is particularily useful for documentation of Elisp
+packages or configurations, since it completes elisp symbols anywere.
 
 On the more experimental side, Cape has the super power to transform Company
 backends into Capfs and merge multiple Capfs into a Super-Capf!



reply via email to

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