From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: Florian Friesdorf <flo@chaoflow.net>, notmuch@notmuchmail.org
Subject: Re: address completion when composing
In-Reply-To: <87fwolh1mu.fsf@eve.chaoflow.net>
References: <87fwolh1mu.fsf@eve.chaoflow.net>
User-Agent: Notmuch/0.5-192-gecd6549 (http://notmuchmail.org) Emacs/23.3.1
	(i486-pc-linux-gnu)
Date: Wed, 11 May 2011 10:49:50 -0400
Message-ID: <87oc39mgvl.fsf@gogo.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: list

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).
> 
> 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.

I certainly agree with this. I've done a pretty craptacular job of
maintaining the python version (just now changed the URL on the wiki,
though, to be fair to myself, I didn't know it was on the wiki in the
first place).

I'd personally argue, not surprisingly, for unifying on the python
version, if unifying we must, just because the python bindings are much
more used than vala bindings (and way more people hack on python than
vala) so it stands a better chance of keeping up with the binary. I
don't see speed as being too much of an issue (either between the two,
or in relation too BBDB), since both are well under a second on my
underpowered netbook and my 6-year-old celeron.

Sebastian might have other opinions, though.

Ideally, though, it would be best if it were part of the bin from the
get-go. Or, even better, if the command-line options made duplicating
the functionality possible.

Best,
Jesse