[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/cape acc33a38dd 2/2: Merge pull request #21 from vifon/
From: |
ELPA Syncer |
Subject: |
[elpa] externals/cape acc33a38dd 2/2: Merge pull request #21 from vifon/patch-1 |
Date: |
Tue, 11 Jan 2022 20:57:17 -0500 (EST) |
branch: externals/cape
commit acc33a38dd43e4466317945f867123731d142bf7
Merge: cf31199bed 8ab924edc5
Author: Daniel Mendler <mail@daniel-mendler.de>
Commit: GitHub <noreply@github.com>
Merge pull request #21 from vifon/patch-1
Fix a typo in README.org
---
README.org | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.org b/README.org
index 55f733080b..d2964fd7d9 100644
--- a/README.org
+++ b/README.org
@@ -28,7 +28,7 @@ trigger the respective completion at point. You can bind them
directly to a key
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.
+packages or configurations, since it completes elisp symbols anywhere.
On the more experimental side, Cape has the super power to transform Company
backends into Capfs and merge multiple Capfs into a Super-Capf! These
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [elpa] externals/cape acc33a38dd 2/2: Merge pull request #21 from vifon/patch-1,
ELPA Syncer <=