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
Date: Sat, 12 Mar 2016 07:24:47 -0400 [thread overview]
Message-ID: <87bn6k6irk.fsf@zancas.localnet> (raw)
In-Reply-To: <1457760049.3681.29.camel@debian.org>
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`.
>
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 ~/.notmuch-config exists,
> 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
next parent reply other threads:[~2016-03-12 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457760049.3681.29.camel@debian.org>
2016-03-12 11:24 ` David Bremner [this message]
2016-03-13 23:13 ` Bug#817964: notmuch: indexing daemon Justus Winter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn6k6irk.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=817964@bugs.debian.org \
--cc=notmuch@notmuchmail.org \
--cc=pabs@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).