unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: George Kadianakis <desnacked@riseup.net>, notmuch@notmuchmail.org
Subject: Re: emacs: How to tab-complete destination email addresses?
Date: Tue, 29 Sep 2020 21:46:38 +0200	[thread overview]
Message-ID: <77f1772faeb80958552f0b93300dbbc6@condition-alpha.com> (raw)
In-Reply-To: <87h7roa3fe.fsf@riseup.net>

Hello George,

George Kadianakis <desnacked@riseup.net> writes:

> [...]
> So what to do?
>
> One way forward is to switch from using notmuch-address to using
> something like bbdb and manually curate my database (since bbdb offers
> this capability).
> [...]

Another option is to use company [1], or any other completion framework
that also offers aggregation of completion candidates from several
sources. In the default configuration, company uses notmuch-address as
one of its message mode back-ends. You can add other sources (e.g. bbdb)
easily, if they're not included in the default config already. LDAP can
also be added via EUDC [2].

[1] http://company-mode.github.io
[2] https://www.gnu.org/software/emacs/manual/html_mono/eudc.html

On a loosely related note: picking the "most relevant", or "best" match
when there's more than one candidate address, is non-trivial. "Least
recently used" is one possible heuristic, but which - when used in
isolation - will likely produce misleading results. If you send a couple
of messages to old addresses, as you described happened to you, that
would push those old addresses up in the ranking. So I guess one would
minimally also need to consider whether those addresses were sent to, or
received from. But then, if someone changes their email address, any
recommendation system would keep suggesting the old address for a
while. Hence, the only solution that works somewhat reliably, to my
experience is linking the lookup with an address book of sorts. When I
update the address book with a new address, I will be presented the new
address at the top of the candidate list.


In short terms, my suggestion is to consider using company, and link it
up with you address book application.


Cheers,

  --alex

      parent reply	other threads:[~2020-09-29 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 16:00 emacs: How to tab-complete destination email addresses? George Kadianakis
2020-09-23 16:20 ` Jameson Graef Rollins
2020-09-24 17:03   ` George Kadianakis
2020-09-24 17:47     ` David Bremner
2020-09-24 20:09       ` Jameson Graef Rollins
2020-09-29 19:46 ` Alexander Adolf [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=77f1772faeb80958552f0b93300dbbc6@condition-alpha.com \
    --to=alexander.adolf@condition-alpha.com \
    --cc=desnacked@riseup.net \
    --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).