From: David Bremner <david@tethera.net>
To: Utkarsh Singh <utkarsh190601@gmail.com>,
Alexander Adolf <alexander.adolf@condition-alpha.com>
Cc: Notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: [PATCH] emacs: Add more front ends for address completion
Date: Wed, 06 Apr 2022 14:23:21 -0400 [thread overview]
Message-ID: <87a6cy9ili.fsf@tethera.net> (raw)
In-Reply-To: <87bkxetndj.fsf@gmail.com>
Utkarsh Singh <utkarsh190601@gmail.com> writes:
>>
>> Can you be more precise about what you are asking / proposing here?
>> Assume I only skimmed the thread.
>
> Currently, notmuch-address.el, the library used to generate completion
> candidates for recipient's addresses in Notmuch's message compostion
> mode uses non-standard Emacs API's for in-buffer completion, namely
> completing-read and Company. Now these API's makes it difficult to
> utilize alternative in-buffer completion UI such as Corfu(1).
#'completing-read is of course standard since forever. We might be using
it in some strange way, or it might be superceded by better things, but
completing-read is not non-standard.
>
> These are the proposed solutions for the given problem:
>
> 1. Add completion-at-point to the existing sets of frontend. As noted
> by Tomi, this is a "messy" solution as it unnecessarily obfuscate the
> user options `notmuch-address-selection-function' and
> `notmuch-address-command'.
>
> 2. Make notmuch-address.el itself a backend for EUDC(2). As stated by
> Alexander, this will not only remove any frontend related code from
> notmuch-address.el, but will also unify completion condidates for other
> sources such as BBDB, LDAP, MacOS Contacts, etc.
>
As a reviewer / release manager, I care about the amount of code
changes. As a user I hope my existing setup will keep working with no,
or (less good) minimal changes. Other than that I am open to ideas.
d
prev parent reply other threads:[~2022-04-06 18:23 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
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 [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
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=87a6cy9ili.fsf@tethera.net \
--to=david@tethera.net \
--cc=alexander.adolf@condition-alpha.com \
--cc=notmuch@notmuchmail.org \
--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).