From: David Bremner <david@tethera.net>
Date: Thu, 24 Mar 2016 12:51:24 +0000 (+2100)
Subject: Re: FastMail uses xapian for real time search, can we do the same?
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=04a55a83cb08efdafe9b9517709fa666821d4c1a;p=notmuch-archives.git

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