From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: Tomi Ollila <tomi.ollila@iki.fi>,
Utkarsh Singh <utkarsh190601@gmail.com>,
Notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: emacs: notmuch-address-command 'as-is throws error (was: [PATCH] emacs: Add more front ends for address completion)
Date: Mon, 28 Feb 2022 22:19:49 +0100 [thread overview]
Message-ID: <ffb9c17d59fb54d36209334fe38dab51@condition-alpha.com> (raw)
In-Reply-To: <m21qzuimn1.fsf@guru.guru-group.fi>
Tomi, apologies for the delay in getting back to you. I'm moving office,
so had a couple of other chores for having fun with. ;-)
Tomi Ollila <tomi.ollila@iki.fi> writes:
> [...]
>> In case not, how can I prevent modification of message-completion-alist
>> by notmuch, and still have notmuch use the 'internal mechanism for
>> generating address completion candidates?
>
> My guess would be some elisp is required...
> [...]
That's a very good first guess. Always. ;-D
I'm happy to have a go at contributing a patch to enable users to use
completion-at-point for address completion. What would be the least
controversial way forward? I can currently think of two variants.
Variant 1 "minimally invasive surgery":
Adding a new, Boolean custom variable which controls modification of
message-completion-alist. notmuch-address-setup would need to be
modified to make use of it.
Pros: "minimally invasive surgery"
Cons: High entry barrier (the end user needs to define his/her own
function producing a completion table for email addresses, and
must hence have a good understanding of how both,
notmuch-address.el, and completion-at-point work).
notmuch-address-command 'as-is retains its not too stringently
defined semantics.
Variant 2 "core Emacs":
Adding a new, choice type custom variable which controls the framework
to use for address completion; possible values are "completing-read
(minibuffer UI)", and "completion-at-point (in-buffer UI)". At the same
time, notmuch-address-use-company and notmuch-address-command 'as-is
would be deprecated. A new function would be added to
notmuch-address.el, which returns a completion table for
completion-at-point. notmuch-address-setup would then need to modified
to add either said new function, or notmuch-address-expand-name to
message-completion-alist, depending on the chosen completion framework
type.
Pros: Uses core Emacs functionality (completing-read, or
completion-at-point), hence removes dependency on 3rd party
packages, and thus would make notmuch-address.el (even) more
future proof.
High-level configuration option lowers entry barrier for end users
(no knowledge of notmuch-address.el, or completion-at-point
required).
Cons: Paves the way for removing company from notmuch-address.el.
Company can use completion-at-point as a back-end (company-capf),
so end users can continue to use company if they wish, but need to
adapt their configuration.
Looking forward to your thoughts,
--alexander
next prev parent reply other threads:[~2022-02-28 21:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 14:38 [PATCH] emacs: Add more front ends for address completion Utkarsh Singh
2022-02-09 21:59 ` Tomi Ollila
2022-02-12 16:09 ` Alexander Adolf
2022-02-21 22:20 ` emacs: notmuch-address-command 'as-is throws error (was: [PATCH] emacs: Add more front ends for address completion) Alexander Adolf
2022-02-22 22:04 ` Tomi Ollila
2022-02-28 21:19 ` Alexander Adolf [this message]
2022-03-01 17:51 ` Alexander Adolf
2022-02-28 9:01 ` [PATCH] emacs: Add more front ends for address completion Utkarsh Singh
2022-03-06 7:28 ` Utkarsh Singh
2022-03-07 22:14 ` Alexander Adolf
[not found] ` <87k0d4n8tr.fsf@gmail.com>
[not found] ` <c6c39f1b36844a9160e81f2f23cb8458@condition-alpha.com>
2022-03-09 1:06 ` Utkarsh Singh
2022-03-11 17:50 ` Alexander Adolf
2022-03-13 3:51 ` Utkarsh Singh
2022-03-15 12:37 ` Alexander Adolf
2022-03-17 4:56 ` Utkarsh Singh
2022-03-20 10:49 ` David Bremner
2022-04-06 12:19 ` Utkarsh Singh
2022-04-06 18:23 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ffb9c17d59fb54d36209334fe38dab51@condition-alpha.com \
--to=alexander.adolf@condition-alpha.com \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
--cc=utkarsh190601@gmail.com \
/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://yhetil.org/notmuch.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).