Re: FastMail uses xapian for real time search, can we do the same?

diff --git a/61/3db1117541cc3b5a1b7e5eeba899a59c0836fa b/61/3db1117541cc3b5a1b7e5eeba899a59c0836fa
new file mode 100644 (file)
index 0000000..8904278
--- /dev/null
+++ b/61/3db1117541cc3b5a1b7e5eeba899a59c0836fa
@@ -0,0 +1,66 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 03A6C6DE02B7\r
+ for <notmuch@notmuchmail.org>; Thu, 24 Mar 2016 05:51:36 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.026\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.026 tagged_above=-999 required=5\r
+ tests=[AWL=-0.015, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]\r
+ autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id kGPD8oMcgEiE for <notmuch@notmuchmail.org>;\r
+ Thu, 24 Mar 2016 05:51:28 -0700 (PDT)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 2C4386DE02AF\r
+ for <notmuch@notmuchmail.org>; Thu, 24 Mar 2016 05:51:28 -0700 (PDT)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1aj4k5-0005US-Ht; Thu, 24 Mar 2016 08:52:01 -0400\r
+Received: (nullmailer pid 18378 invoked by uid 1000);\r
+ Thu, 24 Mar 2016 12:51:24 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Edward Betts <edward@4angle.com>, notmuch@notmuchmail.org\r
+Subject: Re: FastMail uses xapian for real time search, can we do the same?\r
+In-Reply-To: <20160324104033.GA23082@4angle.com>\r
+References: <20160324104033.GA23082@4angle.com>\r
+User-Agent: Notmuch/0.21+74~g6c60fb1 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Thu, 24 Mar 2016 09:51:24 -0300\r
+Message-ID: <87bn64jayb.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 24 Mar 2016 12:51:36 -0000\r
+\r
+Edward Betts <edward@4angle.com> writes:\r
+\r
+>\r
+> Is there any enthusiasm for adding real time search to notmuch?\r
+\r
+It sounds interesting. I do wonder if just better (read, any) retry\r
+handling might give most of the user benefits with fewer moving parts.\r
+\r
+I think the real reason that the locking failures bother me less is just\r
+a workflow one: I don't have notmuch-insert / notmuch-new running in the\r
+background, but rather fetch a few few times a day. I'm not saying\r
+everyone should read mail like I do, just explaining why it's less of a\r
+priority for me personally than some other issues.\r
+\r
+d\r
+\r