From: George Kadianakis <desnacked@riseup.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: emacs: How to tab-complete destination email addresses?
Date: Thu, 24 Sep 2020 20:03:47 +0300 [thread overview]
Message-ID: <87pn6b85u4.fsf@riseup.net> (raw)
In-Reply-To: <87blhw5usy.fsf@caltech.edu>
Jameson Graef Rollins <jrollins@finestructure.net> writes:
> On Wed, Sep 23 2020, George Kadianakis <desnacked@riseup.net> wrote:
>> 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).
>>
>> But I think the right way would be to somehow introduce a bunch of
>> heuristics in notmuch/emacs so that the right email address is chosen
>> for each person. For example, if I tab-complete "Alice", I would like
>> notmuch to give me the email address that Alice has used herself most
>> frequently the past few times she contacted me.
>>
>> Perhaps there is something that does what I want already?
>> If that's the case, I'd love to be pointed to a good solution!
>
Thanks for the response Jameson!
> I find the convenience of not having to maintain an address book to be a
> huge win with the use of notmuch-address, so I'm generally fine to
> filter through the offered addresses to find the one that I generally
> recognize to be the most viable. That said, an obvious improvement (as
> you suggest) would be to order addresses based on most recent+frequent
> use, so that the most recently used one shows up first.
>
So I guess this ordering should happen internally in notmuch-address,
right? Perhaps as a new type of "--sort" option like "--most-frequent"
or "--best-fit".
If this is the right way to do it, perhaps I'll take a stab at it over
the next days. If it's not the right way to do it, please let me know so
that I don't do useless things! :)
> The problem I have, though, is that for some reason that I don't
> understand the interface can use To: address, or From: addresses, but
> not both. This is by far the most annoying thing to me, since in both
> scenarios there will end up being missing addresses that I need that I
> then have to go search for manually. If the interface could be
> configured to return most From: and To: address that would be a big
> improvement imho.
>
Hmm, I've never used this interface but if you are talking about the
"--output" switch I see that they can be combined. So like you can do:
$ notmuch address --output sender --output recipients jameson
to combine both To: and From:.
Best of luck!
next prev parent reply other threads:[~2020-09-24 17:04 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 [this message]
2020-09-24 17:47 ` David Bremner
2020-09-24 20:09 ` Jameson Graef Rollins
2020-09-29 19:46 ` 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=87pn6b85u4.fsf@riseup.net \
--to=desnacked@riseup.net \
--cc=jrollins@finestructure.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).