From: David Bremner <david@tethera.net>
To: Paul Wise <pabs@debian.org>, 817964@bugs.debian.org
Cc: notmuch@notmuchmail.org
Subject: Re: Bug#817964: notmuch: indexing daemon
In-Reply-To: <1457760049.3681.29.camel@debian.org>
References: <1457760049.3681.29.camel@debian.org>
User-Agent: Notmuch/0.21+74~g6c60fb1 (http://notmuchmail.org) Emacs/24.5.1
 (x86_64-pc-linux-gnu)
Date: Sat, 12 Mar 2016 07:24:47 -0400
Message-ID: <87bn6k6irk.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list

Paul Wise <pabs@debian.org> writes:

> I would like to have a daemon running to index my mail as it arrives,
> gets marked read and is deleted. This would ensure that the database is
> up to date when I do a search using notmuch or one of the interfaces.
>
> Right now if I mark a mail as read and try to view it in a notmuch
> frontend then I get an error until I manually run `notmuch new`.=C2=A0
>

Can you describe in more detail what error you are seeing, and how the
file is being marked read?

> I expect the right interface to use for notifications of filesystem
> events is inotify since fanotify doesn't send rename events. This would
> require one inotify per directory.
>
> It would be great if it could autostart when=C2=A0~/.notmuch-config exist=
s,
> using systemd per-user services or perhaps via login autostart stuff.

Currently notmuch doesn't deal very well with e.g. tag changes while
indexing is happening, and my personal feeling is that we should improve
that behaviour first before supporting more concurrency upstream.

d