diff options
| author | Wojciech Siewierski <wojciech@siewierski.eu> | 2022-01-12 01:46:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-12 01:46:51 +0100 |
| commit | 8ab924edc5b8f697ea3dd139cdfdf33438a3482a (patch) | |
| tree | d14496e2a8de1a8d1de8f23717cd8f932d4619fa | |
| parent | cf31199bed3f3b542cb4bc5ca52e372b5e3ac6e3 (diff) | |
Fix a typo in README.org
| -rw-r--r-- | README.org | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -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 |