On Thu, Sep 24 2020, David Bremner <david@tethera.net> wrote:
> George Kadianakis <desnacked@riseup.net> writes:
>
>> 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! :)
>
> there was some discussion about upstreaming some of the features of
> notmuch-addrlookup-c into notmuch-address [1]. I'm not sure what
> happened there, but maybe this helps.

I wasn't aware of notmuch-addrlookup-c as a separate tool, but I just
tried it and it looks like it could be promising.  If it has better
address sorting that definitely seems like something that would be good
to pull in upstream.

>> 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:.
>
> Maybe the elisp 'internal' front-end needs to be updated to (optionally) do what
> Jamie asks.

So I don't think these are the right options to consider, but I'm not
sure.  If I'm searching for addresses associated with the user
"jameson", I think I *don't* want --output=recipients, since I imagine
that includes all the addresses that "jameson" has sent messages *to*,
which is definitely not what I would want included.  But maybe I'm not
understanding.  It seems like emacs must be creating a more nuanced set
of arguments somehow...

jamie.
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org