[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/vertico bac47779a6 3/4: README: Clarify
From: |
ELPA Syncer |
Subject: |
[elpa] externals/vertico bac47779a6 3/4: README: Clarify |
Date: |
Wed, 6 Apr 2022 01:58:22 -0400 (EDT) |
branch: externals/vertico
commit bac47779a66a254f7ee9e20a825d697d5628f6d1
Author: Daniel Mendler <mail@daniel-mendler.de>
Commit: Daniel Mendler <mail@daniel-mendler.de>
README: Clarify
---
README.org | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/README.org b/README.org
index 621cc751e4..05f0d4559e 100644
--- a/README.org
+++ b/README.org
@@ -535,10 +535,11 @@ However the list of possible completions becomes much
more cluttered.
Similar to ~org-refile~, the ~org-agenda-filter~ completion function
(~org-agenda-filter-completion-function~) does not make use of completion
-boundaries. Unfortunately =TAB= completion does not work for this reason. This
-affects Vertico and also the Emacs default completion system. For example if
you
-enter ~+tag<0 TAB~ the input is replaced with ~0:10~ which is not correct. With
-preserved completion boundaries, the expected result would be ~+tag<0:10~.
+boundaries. Unfortunately =TAB= completion (~minibuffer-complete~) does not
work for
+this reason. This affects Vertico and also the Emacs default completion system.
+For example if you enter ~+tag<0 TAB~ the input is replaced with ~0:10~ which
is not
+correct. With preserved completion boundaries, the expected result would be
+~+tag<0:10~.
** ~tmm-menubar~