Re: [PATCH] WIP: regexp matching in 'subject' and 'from'

diff --git a/f8/7b2c4fcafd458c75c3c1c3371d4daf87d2973d b/f8/7b2c4fcafd458c75c3c1c3371d4daf87d2973d
new file mode 100644 (file)
index 0000000..c117524
--- /dev/null
+++ b/f8/7b2c4fcafd458c75c3c1c3371d4daf87d2973d
@@ -0,0 +1,120 @@
+Return-Path: <tomi.ollila@iki.fi>\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 E73936DE01EE\r
+ for <notmuch@notmuchmail.org>; Sat, 11 Jun 2016 10:09:52 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.569\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.569 tagged_above=-999 required=5 tests=[AWL=-0.083,\r
+  SPF_NEUTRAL=0.652] 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 yAFjy2Mk-5xX for <notmuch@notmuchmail.org>;\r
+ Sat, 11 Jun 2016 10:09:44 -0700 (PDT)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 988386DE01BE\r
+ for <notmuch@notmuchmail.org>; Sat, 11 Jun 2016 10:09:44 -0700 (PDT)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+ by guru.guru-group.fi (Postfix) with ESMTP id 30235100104;\r
+ Sat, 11 Jun 2016 20:09:29 +0300 (EEST)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Gaute Hope <eg@gaute.vetsj.com>, David Bremner <david@tethera.net>,\r
+ Austin Clements <aclements@csail.mit.edu>\r
+Cc: notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: [PATCH] WIP: regexp matching in 'subject' and 'from'\r
+In-Reply-To: <1465662533-astroid-3-6vuqm3zu54-1296@strange>\r
+References: <1465265149-7174-1-git-send-email-david@tethera.net>\r
+ <1465525688-30913-1-git-send-email-david@tethera.net>\r
+ <1465547660-astroid-0-nudmv20lbk-1296@strange>\r
+ <87a8itxpu7.fsf@zancas.localnet>\r
+ <1465662533-astroid-3-6vuqm3zu54-1296@strange>\r
+User-Agent: Notmuch/0.22+42~gafaa8cf (https://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-unknown-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+ $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+ !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Sat, 11 Jun 2016 20:09:28 +0300\r
+Message-ID: <m2a8iry7nb.fsf@guru.guru-group.fi>\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: Sat, 11 Jun 2016 17:09:53 -0000\r
+\r
+On Sat, Jun 11 2016, Gaute Hope <eg@gaute.vetsj.com> wrote:\r
+\r
+> David Bremner writes on juni 10, 2016 13:09:\r
+>> Gaute Hope <eg@gaute.vetsj.com> writes:\r
+>> \r
+>>>\r
+>>> Cool!\r
+>>>\r
+>>> Would it break a lot of things if you just replace the original prefix?\r
+>> \r
+>> It would change the matching behaviour. I guess there are people that\r
+>> like the current "sloppy" matching of from: and subject:.  In my\r
+>> not-very-scientific tests, it is a factor of 5 to 10 times slower to do\r
+>> regexp search, which makes sense because it is effectively post\r
+>> processing the results from Xapian. At least on my system it seems fast\r
+>> enough to be usable interactively, but that is a pretty shocking\r
+>> performance regression. And I know there are people with more mail on\r
+>> slower systems.\r
+>\r
+> Maybe we could check if the search string contains a regexp and decide\r
+> whether to pre-process it on the background of that? I think that would\r
+> make the interface more user-friendly. You'd just always use search\r
+> whether you decide that you need to put in some regexp or not.\r
+\r
+You probably wanted to suggest that the command line handling in notmuch\r
+goes through the search terms and potentially modify it before giving\r
+to xapian to chew for... I think this is deliberately avoided (*) -- this\r
+would get out of hands so easily (if we could decide syntax)...\r
+\r
+(*) there is some optmization done before feeding the query to xapian --\r
+but that does not affect interface (i.e. it could be dropped and none of\r
+the users' expectations would be broken...)\r
+\r
+What one can do, is write ones own wrapper around notmuch. I have one\r
+that was written long before notmuch got date: searches (it mangles\r
+e.g 5h.. to 1234567890.. (**) and logs search and show queries\r
+(**) should change that to use date:... instead (i.e. date: queries w/o\r
+date: prefix). I "suggested" subject:/one's own subject re search w// slashes/\r
+which one could pretty easily write to the wrapper...\r
+\r
+Tomi\r
+\r
+>\r
+>> \r
+>>> Could it be made to work on the message body?\r
+>> \r
+>> See Austin's previous reply for the details, but basically no; these\r
+>> "values" index in terms of whole strings, while the body is indexed by\r
+>> terms (roughly, words). In principle we could add a value slot for the\r
+>> body, but I think that would at least double the size of the database\r
+>> (maybe more).\r
+>> \r
+>\r
+> I would rather have double the db and be able wildcard beginning of\r
+> terms. If it is not too much maintaining overhead it might be made\r
+> optional?\r
+>\r
+>\r
+> Regards, Gaute\r
+>\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> https://notmuchmail.org/mailman/listinfo/notmuch\r