From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alexander Adolf <alexander.adolf@condition-alpha.com>
Cc: emacs-devel@gnu.org
Subject: Re: Thoughts on Refactoring In-Buffer Completion In message.el
Date: Wed, 20 Jul 2022 19:59:33 -0400 [thread overview]
Message-ID: <jwvk087jq3p.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5b04a4a1f5a497f030397f6813551ad2@condition-alpha.com> (Alexander Adolf's message of "Wed, 20 Jul 2022 22:59:56 +0200")
> Why restrict it to a table? Perhaps we should allow both, functions and
> tables? Practically, that could mean checking whether the value
> satisfies `functionp`, and `funcall` it when that's the case; else use
> it as a ready-made table.
> It seems I am missing something?
A "completion table" can take several shapes, one of which is
a function. But that function isn't used like a CAPF function.
E.g. `message-expand-name` is a CAPF function whereas
(message--name-table STR) returns a completion table (implemented as a function).
[ I'll get back to you later for the rest of your message. ]
Stefan
next prev parent reply other threads:[~2022-07-20 23:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 15:26 Thoughts on Refactoring In-Buffer Completion In message.el Alexander Adolf
2022-06-25 4:35 ` Thomas Fitzsimmons
2022-06-27 15:48 ` Alexander Adolf
2022-06-25 8:22 ` Stefan Monnier
2022-06-27 16:37 ` Alexander Adolf
2022-06-28 15:49 ` Stefan Monnier
2022-07-19 21:41 ` Alexander Adolf
2022-07-19 22:13 ` Stefan Monnier
2022-07-20 20:59 ` Alexander Adolf
2022-07-20 23:59 ` Stefan Monnier [this message]
2022-07-22 13:20 ` Alexander Adolf
2022-07-22 13:58 ` Alexander Adolf
2022-07-27 21:16 ` Alexander Adolf
2022-08-17 2:45 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2022-08-13 13:11 Alexander Adolf
2022-08-17 1:54 ` Stefan Monnier
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=jwvk087jq3p.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=alexander.adolf@condition-alpha.com \
--cc=emacs-devel@gnu.org \
/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).