From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: Daniel Mendler <mail@daniel-mendler.de>, 56613@debbugs.gnu.org
Subject: bug#56613: 29; minibuffer-complete-history throws an error for minibuffer-history-variable=t
Date: Mon, 18 Jul 2022 11:01:37 -0400 [thread overview]
Message-ID: <jwv35eyii02.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86wncayjaw.fsf@mail.linkov.net> (Juri Linkov's message of "Mon, 18 Jul 2022 10:24:55 +0300")
> But I can't find a function that would return the
> current completion boundaries to use instead of hard-coding
> minibuffer--completion-prompt-end and point-max. Then
> completing-read-multiple should set locally such a function
> that will use crm-separator and return a cons (BEG . END).
I can't remember what hacks are used in CRM, but we do have "a function
that would return the current completion boundaries to use": it's what
`completion-at-point-functions` is for.
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.
Stefan
next prev parent reply other threads:[~2022-07-18 15:01 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 [this message]
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
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=jwv35eyii02.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 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.