branch: externals/corfu
commit 037978eb468c907c8cb3284c1c465152b398fc7e
Author: Daniel Mendler <[email protected]>
Commit: Daniel Mendler <[email protected]>
README: Minor cleanup
---
README.org | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/README.org b/README.org
index 5103fefd56..9bb327322b 100644
--- a/README.org
+++ b/README.org
@@ -395,11 +395,11 @@ force snippet expansion, confirm a candidate explicitly
with ~RET~.
Sometimes it is useful to transfer the Corfu completion session to the
minibuffer, since the minibuffer offers richer interaction features. In
particular, [[https://github.com/oantolin/embark][Embark]] is available in the
minibuffer, such that you can act on the
-candidates or export/collect the candidates to a separate buffer. Hopefully we
-can also add Corfu-support to Embark in the future, such that at least
-export/collect is possible directly from Corfu. But in my opinion having the
-ability to transfer the Corfu completion to the minibuffer is an even better
-feature, since further completion can be performed there.
+candidates or export/collect the candidates to a separate buffer. We could add
+Corfu support to Embark in the future, such that export/collect is possible
+directly from Corfu. But in my opinion having the ability to transfer the Corfu
+completion to the minibuffer is an even better feature, since further
completion
+can be performed there.
The command ~corfu-move-to-minibuffer~ is defined here in terms of
~consult-completion-in-region~, which uses the minibuffer completion UI via
