From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Daniel Bergey <bergey@alum.mit.edu>, notmuch@notmuchmail.org
Subject: Re: notmuch-emacs and bbdb
In-Reply-To: <878ver1jp0.fsf@wonderlust.lan>
References: <878ver1jp0.fsf@wonderlust.lan>
User-Agent: Notmuch/0.13.2+54~ga0426dc (http://notmuchmail.org) Emacs/23.4.1
	(x86_64-pc-linux-gnu)
Date: Wed, 11 Jul 2012 23:43:10 -0700
Message-ID: <87mx35pji9.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Precedence: list

--=-=-=

On Tue, Jul 10 2012, Daniel Bergey <bergey@alum.mit.edu> wrote:
> As far as I can tell, notmuch doesn't integrate as smoothly with bbdb as older
> emacs mailclients.  I'm especially looking for a snarf function that
> distinguishes sender from recipient.
>
> How do other people use bbdb with notmuch?
>
> Does anyone have lisp code like that which ships with bbdb for other
> clients?
>
> If I were to find time to write such code, what would you like it to do?

Hey, Bergey.  This is something that I think needs improvement as well.
I've been just manually constructing the bbdb entries myself.

But what I've really been meaning to get going is address
auto-completion from the database, which I'm pretty sure could obviate
my need for bbdb altogether:

http://notmuchmail.org/emacstips/#index13h2

Getting it working seems more difficult than it should be, though, and
the existing solutions seem a bit slower than they need to be [0].  So I
think there's also room for improvement here.

For instance, I think it would be rad if notmuch provided this
functionality natively, in the CLI, or even in the library [1].  I think
it's definitely doable, and it would be a nice little project.

The emacs integration could be a bit smoother as well.  A single config
option should either turn the functionality on or off.  That would be
very convenient [2].

jamie.

[0] id:"87r4xur3rv.fsf@plc.plecavalier.com"
[1] For what it's worth, I would prefer a solution that didn't involve
    any caching of addresses outside of the database.
[2] I also find it changes the behavior of the ido tab completion
    interface that I'm used to using in message mode.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJP/nH/AAoJEO00zqvie6q8wm8P/3XqMKi5XVynHq7fYeWczAkE
aT4PDRPTLBMiVZuEdhgtBV/6aXMvszX+Bh8uk8VrYoEO7/AijtGNosYIBTHAS/CV
XU372xctZtCAFaySeM7+B711Smqlq1K8aA+n12SOruaPckF6Q001sP/FYN4/P3OO
YtuqDS0ajH06zwgq62WWUioBItWXW1tvbFvH7f0o6PoSUuQfqelRyXNkTGTTZO4z
/UBtd26y6gjTaX41lsd3udYKPmTzbK7VjKFih5EeO1Mj4/9ptPrfrO5gxABr/1XH
0pBE5F/WUg4C3HZoCf+C7pZ0EaXeTmFnFDcQFTSTykEvPkKKiSPnheFire9Q8HGW
r/rLih7V9Lte8VzjOqRTesxZwQyM5yqpIpqmY1NuqDemUj2kfoshGC+NdkDwEMkO
sJ/+7aGWjeMP0IPFczeEbEK9s8r5eMQXiiiRKOOcx6vzY9KO+2kTzD+x2TlgrGkE
KRco+tZqHXNPdOfODTDUFNFsGeW7Eh6WQVdOCqF71vcIHPz9iDh1/JkPttO1vyxh
Fzk7z121MgxsBDYo9CIfA4XQjHYKes+SDOZHvfm4Udlc9OL2C5S2tnnR7wprYV4t
/n88cTBItXlOC5zkmxTilQx9F4lBYc4cE+Ub7ktgx3OZLMHv/67WTP3LYCOwlbSz
GjNm5o4htWIHNV76Phs0
=hgJT
-----END PGP SIGNATURE-----
--=-=-=--