Re: [notmuch] Git as notmuch object store (was: Potential problem using Git for mail)

Subject: Re: [notmuch] Git as notmuch object store (was: Potential problem using Git for mail)

Date: Wed, 27 Jan 2010 10:00:47 +0100

To: martin f krafft, Asheesh Laroia

Cc: notmuch

From: Sebastian Spaeth

On Mon, 25 Jan 2010 14:49:00 +0100, "Sebastian Spaeth" <Sebastian@SSpaeth.de> wrote:
> While notmuchsync fullfils my needs, it is a kludge. It needs to call
> "notmuch" for each mail where a MailDir flag has changed (which can be
> quite often on an initial run, where most mails are likely to be read),
> this can take a long, long time. It would makes sense IMHO to at least
> pick pioto's "don't set unread if 'S' flag is set" on notmuch new[1].

Once python bindings exist for the notmuch shared library, I am sure we
can speed notmuchsync up a lot by keeping the connection open and
tagging all mails in one go rather than executing a separate binary for
each mail. So, this approach might still be feasible.
Sebastian

Thread: