From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 4A3C16DE13EF for ; Sat, 12 Mar 2016 03:24:56 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.033 X-Spam-Level: X-Spam-Status: No, score=-0.033 tagged_above=-999 required=5 tests=[AWL=-0.022, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cqb7oh16WROO for ; Sat, 12 Mar 2016 03:24:54 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 6E4326DE13DA for ; Sat, 12 Mar 2016 03:24:54 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1aehfi-00049c-FG; Sat, 12 Mar 2016 06:25:26 -0500 Received: (nullmailer pid 29497 invoked by uid 1000); Sat, 12 Mar 2016 11:24:47 -0000 From: David Bremner To: Paul Wise , 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 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2016 11:24:56 -0000 Paul Wise 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