Re: searching: '*analysis' vs 'reanalysis'

diff --git a/0d/ca391b97c0fb77b9fbe56a3fee06ba5e8c6bfb b/0d/ca391b97c0fb77b9fbe56a3fee06ba5e8c6bfb
new file mode 100644 (file)
index 0000000..a24cc4d
--- /dev/null
+++ b/0d/ca391b97c0fb77b9fbe56a3fee06ba5e8c6bfb
@@ -0,0 +1,80 @@
+Return-Path: <aclements@csail.mit.edu>\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 A27496DE0130\r
+ for <notmuch@notmuchmail.org>; Mon,  6 Jun 2016 13:22:32 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.304\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.304 tagged_above=-999 required=5\r
+ tests=[AWL=-0.293, 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 FEl2IQvXzlt2 for <notmuch@notmuchmail.org>;\r
+ Mon,  6 Jun 2016 13:22:25 -0700 (PDT)\r
+Received: from outgoing-tmp.csail.mit.edu (outgoing-tmp.csail.mit.edu\r
+ [128.30.2.206])\r
+ by arlo.cworth.org (Postfix) with ESMTP id EA27C6DE00DA\r
+ for <notmuch@notmuchmail.org>; Mon,  6 Jun 2016 13:22:24 -0700 (PDT)\r
+Received: from awakening.a20.io ([104.131.20.129] helo=awakening)\r
+ by outgoing-tmp.csail.mit.edu with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128)\r
+ (Exim 4.82) (envelope-from <aclements@csail.mit.edu>)\r
+ id 1bA12T-0004KF-Dy; Mon, 06 Jun 2016 16:22:21 -0400\r
+Received: from amthrax by awakening with local (Exim 4.86)\r
+ (envelope-from <aclements@csail.mit.edu>)\r
+ id 1bA12S-0005II-Oi; Mon, 06 Jun 2016 16:22:20 -0400\r
+Date: Mon, 6 Jun 2016 16:22:15 -0400\r
+From: Austin Clements <aclements@csail.mit.edu>\r
+To: Gaute Hope <eg@gaute.vetsj.com>\r
+Cc: David Bremner <david@tethera.net>, sfischme@uwaterloo.ca,\r
+ notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: searching: '*analysis' vs 'reanalysis'\r
+Message-ID: <20160606202215.GE7854@csail.mit.edu>\r
+References: <1465196150-astroid-3-33kf2otxir-16915@strange>\r
+ <87lh2ijxor.fsf@tesseract.cs.unb.ca>\r
+ <1465217156-astroid-4-8l08w9cils-2318@strange>\r
+ <877fe2tiy8.fsf@uwaterloo.ca> <878tyins3j.fsf@tesseract.cs.unb.ca>\r
+ <CAH-f9WtC6CeVecfg8wFZUVc8K2rUfzsP72xo97sJX2y_mLW6-g@mail.gmail.com>\r
+ <1465243657-astroid-0-zfssqjwtff-28912@strange>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <1465243657-astroid-0-zfssqjwtff-28912@strange>\r
+User-Agent: Mutt/1.5.24 (2015-08-30)\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: Mon, 06 Jun 2016 20:22:32 -0000\r
+\r
+Quoth Gaute Hope on Jun 06 at  8:08 pm:\r
+> Austin Clements writes on juni 6, 2016 21:20:\r
+> >\r
+> >The experiment was specifically for regexp matching subject, but it should\r
+> >work for any header we store a literal copy of in the database.\r
+> \r
+> Does it work for terms in the body of the message?\r
+\r
+No. It's not impossible that it could be made to work, but it might be\r
+slow and unintuitive. It would have to iterate over all of the terms\r
+in the database and see which ones match the regexp. These are\r
+available, but I don't know how much time it takes to iterate over all\r
+of them. It might be okay. It might not.\r
+\r
+It could also expand to a very large query if the regexp matches many\r
+terms, akin to how searching for "a*" can be quite expensive.\r
+\r
+And it might not match what you expect. It could only match individual\r
+terms, so a regexp containing any punctuation (including but not\r
+limited to a space) simply wouldn't match anything.\r