[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/vertico 60554ca: Expand README
From: |
ELPA Syncer |
Subject: |
[elpa] externals/vertico 60554ca: Expand README |
Date: |
Sat, 13 Nov 2021 05:57:29 -0500 (EST) |
branch: externals/vertico
commit 60554ca0ec23c8ad47367b12d5ba5d5a5955a098
Author: Daniel Mendler <mail@daniel-mendler.de>
Commit: Daniel Mendler <mail@daniel-mendler.de>
Expand README
---
README.org | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/README.org b/README.org
index bdad338..c34cb33 100644
--- a/README.org
+++ b/README.org
@@ -322,21 +322,31 @@ packages a try and judge for yourself.
There are other interactive completion UIs, which follow a similar
philosophy:
- - [[https://github.com/raxod502/selectrum][Selectrum]]: Selectrum has a
similar UI as Vertico. Selectrum is more complex
- and not fully compatible with every Emacs completion command
([[https://github.com/raxod502/selectrum/issues/481][Issue #481]]),
- since it uses its own filtering infrastructure, which deviates from the
- standard Emacs completion facilities. Vertico additionally has the ability
- to cycle over candidates, offers commands for grouping support and comes
- with a rich set of [[#extensions][extensions]].
+ - [[https://github.com/raxod502/selectrum][Selectrum]]: Selectrum has a
similar UI as Vertico, since it directly inspired
+ Vertico. The Selectrum code base is more complex. Unfortunately Selectrum
is
+ not fully compatible with every Emacs completion command
([[https://github.com/raxod502/selectrum/issues/481][Issue #481]]), since
+ it uses its own filtering infrastructure, which deviates from the standard
+ Emacs completion facilities. Vertico additionally has the ability to cycle
+ over candidates, offers commands for grouping support and comes with a rich
+ set of [[#extensions][extensions]].
- [[https://github.com/oantolin/icomplete-vertical][Icomplete-vertical]]:
This package enhances the Emacs builtin Icomplete with a
vertical display. In contrast to Vertico, Icomplete rotates the candidates
such that the current candidate always appears at the top. From my
perspective, candidate rotation feels a bit less intuitive than the UI of
Vertico or Selectrum. Note that Emacs 28 offers a built-in
~icomplete-vertical-mode~.
- - [[https://gitlab.com/protesilaos/mct][Mct]]: Minibuffer and Completions in
Tandem. Mct reuses the default completions
+ - [[https://gitlab.com/protesilaos/mct][Mct]]: Minibuffer and Completions in
Tandem. Mct reuses the default ~*Completions*~
buffer and enhances it with automatic updates and additional keybindings,
to
- select a candidate and move between minibuffer and completions buffer.
+ select a candidate and move between minibuffer and completions buffer. Mct
+ 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.
* Problematic completion commands
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [elpa] externals/vertico 60554ca: Expand README,
ELPA Syncer <=