From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
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 12:19:32 -0400 [thread overview]
Message-ID: <jwv8roqgzu2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5646a09b-6360-2290-d0c9-671c8216ad69@daniel-mendler.de> (Daniel Mendler's message of "Mon, 18 Jul 2022 17:39:10 +0200")
>> 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.
How to make that interact correctly with packages like `icomplete-mode`
which have been designed specifically for minibuffer completion is part
of the implementation issues.
Stefan
next prev parent reply other threads:[~2022-07-18 16:19 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 [this message]
2022-07-18 17:27 ` Daniel Mendler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv8roqgzu2.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=56613@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=mail@daniel-mendler.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).