[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/vertico 92616a0459 1/2: README: Mention that Mct suppor
From: |
ELPA Syncer |
Subject: |
[elpa] externals/vertico 92616a0459 1/2: README: Mention that Mct supports completion in region |
Date: |
Sat, 1 Jan 2022 19:57:58 -0500 (EST) |
branch: externals/vertico
commit 92616a0459006842494b0835f136c088bb7ee48b
Author: Daniel Mendler <mail@daniel-mendler.de>
Commit: Daniel Mendler <mail@daniel-mendler.de>
README: Mention that Mct supports completion in region
---
README.org | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/README.org b/README.org
index 9451127e05..1baf96262e 100644
--- a/README.org
+++ b/README.org
@@ -456,12 +456,12 @@ packages a try and judge for yourself.
is great if you prefer an unobtrusive UI since it can be configured to open
only when requested. Furthermore since Mct uses a fully functional buffer
you can reuse all your familar buffer commands inside the completions
- buffer. The main distinction to an approach like Vertico's is that
- ~*Completions*~ buffer displays all matching candidates. On the one hand
this
- is good since it allows you to interact with all the candidates and jump
- around with Isearch or Avy. On the other hand it necessarily causes a small
- slowdown in comparison to Vertico, which only displays a small subset of
- candidates.
+ buffer. The main distinction to Vertico's approach is that ~*Completions*~
+ buffer displays all matching candidates. On the one hand this is good since
+ it allows you to interact with all the candidates and jump around with
+ Isearch or Avy. On the other hand it necessarily causes a slowdown in
+ comparison to Vertico, which only displays a subset of candidates. Mct
+ supports completion in region via its ~mct-region-mode~.
* Problematic completion commands