Why kernel development still uses email (2016)

Re:Why kernel development still uses email (2016) by pmoriarty on Saturday September 30, 2017 @04:39PM (#15374883)

Autocompletion from the notmuch database is fine when you don't have many addresses in there. But when you are subscribed to a bunch of large mailing lists and you try to search your notmuch database for "John" you're going to get a thousand completion candidates.

If instead you search just your BBDB database, which only has the contacts you actually correspond with, you're going to get just the useful and relevant ones... and you'll always have the notmuch database to search on as a backup, in case the contact you want to to correspond with is not in BBDB yet.

[ Parent | on HN ]

Re:Why kernel development still uses email (2016) by nextos on Saturday September 30, 2017 @04:56PM (#15374945)

Sure, all these points are true. Notmuch is a bit unfinished I think. What email setup do you have?

[ Parent | on HN ]

Re:Why kernel development still uses email (2016) by pmoriarty on Saturday September 30, 2017 @06:30PM (#15375315)

I'm actually using notmuch in emacs myself, but I'm just running in to a bunch of its limitations and looking around for an alternative.

Very sorry to hear that Gnus with a notmuch backend is slow, as that's what I was considering trying next.

[ Parent | on HN ]

Re:Why kernel development still uses email (2016) by nextos on Saturday September 30, 2017 @08:24PM (#15375740)

Maybe give Gnus a try anyway. It might not be that slow on good hardware. Or just run it coupled with a Dovecot server.

I really like Notmuch's interface. I think limitations are perhaps not that hard to patch on Elisp unless you have a complicated setup.

I'm trying to implement a DSL to coordinate tag <-> maildir sync on top of a few macros.

[ Parent | on HN ]