From: Sebastien Binet <seb.binet@gmail.com>
To: Florian Friesdorf <flo@chaoflow.net>, notmuch@notmuchmail.org
Subject: Re: address completion when composing
Date: Wed, 11 May 2011 14:40:47 +0200 [thread overview]
Message-ID: <87k4dxfm0g.fsf@cern.ch> (raw)
In-Reply-To: <87fwolh1mu.fsf@eve.chaoflow.net>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Wed, 11 May 2011 14:18:01 +0200, Florian Friesdorf <flo@chaoflow.net> wrote:
>
> According to the docs [1], there are two programs that can be used with
> notmuch-address.el: notmuch-addresses (python) and addrlookup
> (vala/c).
for completeness...
there is also notmuch-addrlookup in go:
http://git.notmuchmail.org/git/notmuch/tree/HEAD:/bindings/go/cmds
(which is broken with the latest go release r57.1 because one of the 3rd
party package (to parse config files) is broken...)
>
> Further it is possible to import all addresses into bbdb [2], supposedly
> faster than notmuch-address.el.
>
> Is it also faster than notmuch-address.el + addrlookup?
presumably: crawling thru the db is I/O bound...
> What about shipping some / all of these with notmuch? It feels that
> newbies would benefit from this inclusion and more extensive
> documentation about what to do to get address completion.
>
> Probably it would be sane to decide either for notmuch-addresses or
> addrlookup, as they seem to do the same.
>
> In addition the import script for bbdb could be nice.
+1
-s
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-05-11 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 12:18 address completion when composing Florian Friesdorf
2011-05-11 12:31 ` Florian Friesdorf
2011-05-11 17:18 ` Jameson Graef Rollins
2011-05-12 0:04 ` Florian Friesdorf
2011-05-12 7:38 ` Jameson Graef Rollins
2011-05-16 20:04 ` Sebastian Spaeth
2011-05-17 0:30 ` Carl Worth
2011-05-11 12:40 ` Sebastien Binet [this message]
2011-05-11 14:49 ` Jesse Rosenthal
2011-05-11 20:43 ` Sebastian Spaeth
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=87k4dxfm0g.fsf@cern.ch \
--to=seb.binet@gmail.com \
--cc=flo@chaoflow.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).