From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: notmuch@notmuchmail.org
Subject: [Emacs] Using notmuch-address with EUDC, and completion-at-point
Date: Fri, 22 Jul 2022 16:50:21 +0200 [thread overview]
Message-ID: <8a437e3f646f7972c86c4aae57ae7452@condition-alpha.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Hello,
I recently switched in-buffer completion from company [1] to
completion-at-point with corfu [2] as the UI.
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
To close the loop, I also wrote an EUDC back-end to get candidates from
notmuch-address (which attached).
Now, with a eudc-server-hotlist value of
(("localhost" . notmuch-address)
("localhost" . macos-contacts))
and eudc-capf-complete among completion-at-point-functions in
message-mode, I get combined email address completion candidates from
both sources offered by completion-at-point when composing a new email.
Life can be a breeze at times... ;-)
I hope anyone else finds this useful.
Hoping to have helped, and looking forward to your thoughts,
--alexander
[-- Attachment #2: eudcb-notmuch-address.el --]
[-- Type: application/emacs-lisp, Size: 3378 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2022-07-22 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 14:50 Alexander Adolf [this message]
2022-07-30 12:37 ` [Emacs] Using notmuch-address with EUDC, and completion-at-point David Bremner
2022-08-02 15:26 ` Alexander Adolf
2022-08-12 10:28 ` David Bremner
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=8a437e3f646f7972c86c4aae57ae7452@condition-alpha.com \
--to=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).