From: Daniel Mendler <mail@daniel-mendler.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 56613@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#56613: 29; minibuffer-complete-history throws an error for minibuffer-history-variable=t
Date: Mon, 18 Jul 2022 19:27:18 +0200 [thread overview]
Message-ID: <b6fb1f4b-38c3-9a5c-fea2-785b65e755af@daniel-mendler.de> (raw)
In-Reply-To: <jwv8roqgzu2.fsf-monnier+emacs@gnu.org>
On 7/18/22 18:19, Stefan Monnier wrote:
>>> I think the long-term direction is clear: `completion-at-point` should
>>> be used not just "in buffer" but in the minibuffer as well.
>>> We could start that journey by making use of it for CRM.
>>
>> Not sure if I agree with this in full generality. The question is if you
>> define completion only as completion of text or if you also accept the
>> selection paradigm, where are a bunch of candidates are offered and
>> filtered. The selection paradigm is used in most popular applications
>> (web browser history, form filling). In Emacs we have Icomplete, Ivy,
>> Vertico, etc. which implement that paradigm.
>
> I wasn't careful enough in what I wrote. I didn't mean to say that CRM
> should use the `completion-at-point` UI, but that it should rely on CAPF
> as the way to complete each element.
Oh, I already agreed that Capfs could work for CRM behind the scenes.
However I would be careful to not violate the abstraction barriers too
much, which we have in place right now. In the end the completion table
has to be passed through completing-read or completion-in-region to the
frontend.
(completing-read-multiple installs its crm--choose-completion-string
hook, which is not great. But besides that, it is kind of nice that
completing-read and completing-read-multiple just work as is with
Vertico. Vertico doesn't have any kind of CRM special casing.)
Daniel
prev parent reply other threads:[~2022-07-18 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 11:41 bug#56613: 29; minibuffer-complete-history throws an error for minibuffer-history-variable=t Daniel Mendler
2022-07-17 14:43 ` Drew Adams
2022-07-17 14:53 ` Daniel Mendler
2022-07-17 15:32 ` Drew Adams
2022-07-17 18:07 ` Juri Linkov
2022-07-17 20:10 ` Daniel Mendler
2022-07-18 7:24 ` Juri Linkov
2022-07-18 7:41 ` Daniel Mendler
2022-07-18 15:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 15:21 ` Daniel Mendler
2022-07-18 15:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 15:39 ` Daniel Mendler
2022-07-18 16:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 17:27 ` Daniel Mendler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6fb1f4b-38c3-9a5c-fea2-785b65e755af@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=56613@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.