branch: externals/cape
commit 4b7b45c08ef5ff261616d7e321d1318539b5872e
Author: Daniel Mendler <m...@daniel-mendler.de>
Commit: Daniel Mendler <m...@daniel-mendler.de>
Remove stability warning
---
README.org | 9 ++++-----
cape.el | 14 +++++---------
2 files changed, 9 insertions(+), 14 deletions(-)
diff --git a/README.org b/README.org
index 1e935458ed..9e12b4fb58 100644
--- a/README.org
+++ b/README.org
@@ -65,7 +65,7 @@ Furthermore the =cape-*= functions are Capfs which you can
add to the
since each of the Capfs adds a small runtime cost. Note that the Capfs which
occur earlier in the list take precedence, such that the first Capf returning a
result will win and the later Capfs may not get a chance to run. In order to
-merge Capfs you can try the experimental function =cape-capf-super=.
+merge Capfs you can try the function =cape-capf-super=.
One must distinguish the buffer-local and the global value of the
=completion-at-point-functions= variable. The buffer-local value of the list
takes
@@ -193,10 +193,9 @@ with ~cape-capf-super~.
/Throw multiple Capfs under the Cape and get a Super-Capf!/
-Cape supports merging multiple Capfs using the function ~cape-capf-super~. This
-feature is *EXPERIMENTAL* and should only be used carefully in special
scenarios.
-Due to some technical details, not all Capfs can be merged successfully. Merge
-Capfs one by one and make sure that you get the desired outcome.
+Cape supports merging multiple Capfs using the function ~cape-capf-super~. Due
to
+some technical details, not all Capfs can be merged successfully. Merge Capfs
+one by one and make sure that you get the desired outcome.
Note that ~cape-capf-super~ is not needed if multiple Capfs should betried one
after the other, for example you can use ~cape-file~ together with programming
diff --git a/cape.el b/cape.el
index adab1f1622..e7d09b6627 100644
--- a/cape.el
+++ b/cape.el
@@ -816,11 +816,10 @@ If INTERACTIVE is nil the function acts like a Capf."
;;;###autoload
(defun cape-company-to-capf (backend &optional valid)
"Convert Company BACKEND function to Capf.
-VALID is a function taking the old and new input string. It
-should return nil if the cached candidates became invalid. The
-default value for VALID is `string-prefix-p' such that the
-candidates are only fetched again if the input prefix
-changed. The function `cape-company-to-capf' is experimental."
+VALID is a function taking the old and new input string. It should
+return nil if the cached candidates became invalid. The default value
+for VALID is `string-prefix-p' such that the candidates are only fetched
+again if the input prefix changed."
(lambda ()
(when (and (symbolp backend) (not (fboundp backend)))
(ignore-errors (require backend nil t)))
@@ -909,10 +908,7 @@ multiple super Capfs in the
`completion-at-point-functions':
(list (cape-capf-super \\='eglot-completion-at-point
:with \\='tempel-complete)
(cape-capf-super \\='cape-dabbrev
- :with \\='tempel-complete)))
-
-The functions `cape-wrap-super' and `cape-capf-super' are
-experimental."
+ :with \\='tempel-complete)))"
(when-let ((results (cl-loop for capf in capfs until (eq capf :with)
for res = (funcall capf)
if res collect (cons t res))))
