unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Alexander Adolf <alexander.adolf@condition-alpha.com>,
	notmuch@notmuchmail.org
Subject: Re: [Emacs] Using notmuch-address with EUDC, and completion-at-point
Date: Fri, 12 Aug 2022 07:28:56 -0300	[thread overview]
Message-ID: <871qtlhi1j.fsf@tethera.net> (raw)
In-Reply-To: <a9ee88d939a1fedee389b37fbc6f4a64@condition-alpha.com>

Alexander Adolf <alexander.adolf@condition-alpha.com> writes:

> Hello David,
>
> thanks for your comments and questions.
>
> David Bremner <david@tethera.net> writes:
>
>> Alexander Adolf <alexander.adolf@condition-alpha.com> writes:
>>
>>> As I wanted email address completion via completion-at-point in
>>> message-mode too, I implemented a new EUDC function to go into
>>> completion-at-point-functions [3].
>>>
>>> [1] https://company-mode.github.io
>>> [2] https://github.com/minad/corfu
>>> [3] https://github.com/emacs-mirror/emacs/blob/master/lisp/net/eudc-capf.el
>>>
>>
>> I will have to leave to others to test this, since I'm personally still
>> running emacs 27 (and that is likely to continue for a while, at least
>> on some machines).
>
> You could do
>
>      (require 'eudcb-notmuch-address)
>      (eudc-notmuch-address-set-server "localhost")
>
> and bind the function eudc-expand-inline to a key chord of your choice
> in message-mode-map.
>
> Then you'd no longer have to tweak message-completion-alist.

I stopped my investigations at the point it looked like I needed to edit
notmuch-address.el. I guess another patch or two is needed to do notmuch
integration. And of course we would need tests (in the notmuch test
suite) and documentation before actually merging the functionality, but
those can probably wait until we have a clearer idea what benefits the
change would bring.

> This assumes that eudc-expand-inline is present in Emacs 27, of course,
> which I admittedly haven't checked.

The function exists here in Emacs 27.1.

> What you'd probably lose (or no longer need, whichever way you view it)
> is any company-mode integration.

Unless the UX is very close, some people will strongly prefer to stay
with the existing completion, so I guess we'd need to make it
opt-in. Unfortunately as Tomi already pointed out the configuration is
already a bit of a confusing mess.

  reply	other threads:[~2022-08-12 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 14:50 [Emacs] Using notmuch-address with EUDC, and completion-at-point Alexander Adolf
2022-07-30 12:37 ` David Bremner
2022-08-02 15:26   ` Alexander Adolf
2022-08-12 10:28     ` David Bremner [this message]
2022-08-16 17:35       ` Alexander Adolf
2022-08-18 14:57         ` David Bremner
2022-08-18 21:31           ` Alexander Adolf

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=871qtlhi1j.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=alexander.adolf@condition-alpha.com \
    --cc=notmuch@notmuchmail.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://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).