[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/mct ea0847d 50/70: Update "Alternatives" section; add E
From: |
ELPA Syncer |
Subject: |
[elpa] externals/mct ea0847d 50/70: Update "Alternatives" section; add Elmo |
Date: |
Thu, 11 Nov 2021 03:57:50 -0500 (EST) |
branch: externals/mct
commit ea0847d5968e7045e69b1d23b5acdaac3328239a
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>
Update "Alternatives" section; add Elmo
---
README.org | 44 ++++++++++++++++++++++++++++++++++++++++----
1 file changed, 40 insertions(+), 4 deletions(-)
diff --git a/README.org b/README.org
index 77453a6..b680fb5 100644
--- a/README.org
+++ b/README.org
@@ -471,10 +471,46 @@ these exceptionally well-crafted extras:
:END:
#+cindex: Alternatives to MCT
-The only alternative I have used that is conceptually close to MCT is
-=vertico=. Vertico is a more mature and feature-rich package, while its
-maintainer, Daniel Mendler, is an accomplished programmer. Whereas MCT
-is mostly an excuse to practice my Elisp skills.
++ [[https://github.com/minad/vertico][Vertico]] by Daniel Mendler :: this is a
more mature and feature-rich
+ package with a large user base, while its maintainer is an
+ accomplished programmer. Whereas MCT is mostly an excuse to practice
+ my Elisp skills.
+
+ Just like MCT, Vertico works with the standard ~completing-read~
+ infrastructure, so it makes for a natural complement to the standard
+ Emacs experience.
+
+ The main difference between Vertico and MCT is that the former uses
+ the minibuffer by default and shows the completions there. Whereas
+ MCT keeps the =*Completions*= buffer and the minibuffer as separate
+ entities, the way standard Emacs does it.
+
+ The presence of a fully fledged buffer means that the user can invoke
+ all relevant commands at their disposal, such as to write the buffer
+ to a file for future review, use Isearch to move around, copy a string
+ or rectangle to a register, and so on.
+
+ Vertico can optionally use a standalone buffer as well, by means of an
+ extension found in Vertico's git repository, so this is not a major
+ point anyway. Plus, users of Embark can always create a buffer out of
+ any list of completions.
+
++ [[https://github.com/karthink/elmo][Elmo - Embark Live MOde for Emacs]] by
Karthik Chikmagalur :: this
+ package is best described as a sibling of MCT both in terms of its
+ functionality and overall interaction model. In fact, the cyclic
+ motions that are at the core of the MCT experience were first
+ developed as part of my personal Emacs setup to cycle between the
+ minibuffer and Embark's "live completions" buffer. That was until
+ Emacs28 got some refinements to the presentation of the =*Completions*=
+ buffer which allowed for a vertical, single-column view.
+
+ Elmo can, in principle, have identical functionality with MCT, given
+ that the only substantive difference is that the former uses an Embark
+ buffer to show live-updating completions, while the latter relies on
+ the generic =*Completions*= buffer.
+
+ For users who are on Emacs 27, Elmo is a better choice because MCT
+ only works as intended with Emacs 28 or higher.
* Acknowledgements
:PROPERTIES:
- [elpa] externals/mct e7f13ee 43/70: Make TAB in the Completions never exit, (continued)
- [elpa] externals/mct e7f13ee 43/70: Make TAB in the Completions never exit, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 97d7855 45/70: Use correct internals for commit 099e204, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 532656b 54/70: Merge branch 'crm-separator-heuristic' into 'main', ELPA Syncer, 2021/11/11
- [elpa] externals/mct 78f3e77 57/70: Clear trailing space, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 573a324 60/70: Document numeric arg for cyclic commands, ELPA Syncer, 2021/11/11
- [elpa] externals/mct d333057 59/70: Update keys for group navigation, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 981dba1 68/70: Fix typo, ELPA Syncer, 2021/11/11
- [elpa] externals/mct e459304 64/70: Add missing reference to mct-backward-updir, ELPA Syncer, 2021/11/11
- [elpa] externals/mct b5f4222 70/70: Update Acknowledgements in the manual, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 57cd47d 69/70: Expand mct-live-update; update documentation, ELPA Syncer, 2021/11/11
- [elpa] externals/mct ea0847d 50/70: Update "Alternatives" section; add Elmo,
ELPA Syncer <=
- [elpa] externals/mct 5972191 51/70: Update docs on Alternatives; improve vertico part, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 01edefb 14/70: Use memq instead of member where applicable, ELPA Syncer, 2021/11/11
- [elpa] externals/mct c096fab 48/70: Mention completion-cycle-threshold in the manual, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 6eefd80 49/70: Expand the "extensions" section in the manual, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 20aa296 52/70: Heuristic attempt to handle different CRM separator, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 8f8a83a 39/70: Make mct-edit-completion behave consistently, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 9586c51 41/70: Refine mct-choose-completion{, -no}-exit, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 4d61a41 46/70: Minor tweaks to code sample in the manual, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 2dd1308 53/70: Add functions to jump through completion groups in completions, ELPA Syncer, 2021/11/11
- [elpa] externals/mct 47b26e4 61/70: Document group motions and backward-dir motion, ELPA Syncer, 2021/11/11