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

diff --git a/8e/e30789937cbeb1554741a0f96fe1881e6d1682 b/8e/e30789937cbeb1554741a0f96fe1881e6d1682
new file mode 100644 (file)
index 0000000..fce2306
--- /dev/null
+++ b/8e/e30789937cbeb1554741a0f96fe1881e6d1682
@@ -0,0 +1,120 @@
+Return-Path: <eg@gaute.vetsj.com>\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 C99756DE01C2\r
+ for <notmuch@notmuchmail.org>; Sat, 11 Jun 2016 10:34:31 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.565\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.565 tagged_above=-999 required=5 tests=[AWL=0.155,\r
+  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7,\r
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 p0F5eVkCgjeh for <notmuch@notmuchmail.org>;\r
+ Sat, 11 Jun 2016 10:34:24 -0700 (PDT)\r
+Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com\r
+ [74.125.82.45]) by arlo.cworth.org (Postfix) with ESMTPS id 7E4006DE01BE for\r
+ <notmuch@notmuchmail.org>; Sat, 11 Jun 2016 10:34:23 -0700 (PDT)\r
+Received: by mail-wm0-f45.google.com with SMTP id n184so28276863wmn.1\r
+ for <notmuch@notmuchmail.org>; Sat, 11 Jun 2016 10:34:23 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=gaute-vetsj-com.20150623.gappssmtp.com; s=20150623;\r
+ h=date:from:subject:to:cc:references:in-reply-to:user-agent\r
+ :message-id:mime-version:content-transfer-encoding;\r
+ bh=3BWrb6KhiigNniko+Rcyy3yVbGdB+pbvHQrHqruAOns=;\r
+ b=zRHIhYAcUQOtxWhQtun7X/FAkdr0tzK3sYALumyl4pgsq/IvwDYm2IvQMYn3AcbaCb\r
+ JqBtYQQhGX1u5KB0EGttRH+LCgLxmYJb0X7+n8gX9IWFITmr8+Y8zOhxPz+mixl5Vml6\r
+ udnwbMfVqYrTq8mIcA7mxg1/adJVJl0OnegAyirINH+QaLrixzHJNRBjAXvzARFUEJwQ\r
+ b4BSl0nIKoj4VQuyyLbqsUnHpB5k3wg8wjmZF++ysxNz3VelblyIbpSvH2Ii1CJ0r/00\r
+ T3Caj8kpDIzS1KxyN4Qfs0d2XhqPEdeeL424e0uaYhUQoLCuHF8uFgwVYLHg0d9jWB7h\r
+ 94Kg==\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=1e100.net; s=20130820;\r
+ h=x-gm-message-state:date:from:subject:to:cc:references:in-reply-to\r
+ :user-agent:message-id:mime-version:content-transfer-encoding;\r
+ bh=3BWrb6KhiigNniko+Rcyy3yVbGdB+pbvHQrHqruAOns=;\r
+ b=acwYMVNYccWsuL5yJbZ0fbDg565rkJ3UuTpHmj6aRdNHZoYa3aBxDccs13ihySI+4l\r
+ kOWYmuPx6J1DFhy4mLs9HrmMpPFlciAK13/1CT4+1G+fIbC/MAkKArGfqzMNRb2DxZhN\r
+ XEzz9zTgZqLAOhZb/FoKJxNIDDDOjs2sEAKMwc6tXgSQ541w0DIO4d1Vt/1YaxCwac7h\r
+ 03U9bANi2QS3NE/A9CizD6GNk2OpCfMSnFRIF5sUbjSUFTXU2fJmSuRVYx5eOZPC2e3v\r
+ PSAEl4EWhKYzPL8FFGZWATeR+WxEPulOEueJJxFiiarIxk9eqNeic8Mj+YQ+8/xwPW8N\r
+ Arng==\r
+X-Gm-Message-State:\r
+ ALyK8tIi8esYnQP90dAuj8NGH3msAtErAbcRkJZnD8C4HeTmPwJBvJnxjR3Orir+42emNQ==\r
+X-Received: by 10.194.133.135 with SMTP id pc7mr7314542wjb.49.1465666461824;\r
+ Sat, 11 Jun 2016 10:34:21 -0700 (PDT)\r
+Received: from localhost (241.89-20-241.enivest.net. [89.20.241.241])\r
+ by smtp.gmail.com with ESMTPSA id k127sm5047077wmf.21.2016.06.11.10.34.20\r
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Sat, 11 Jun 2016 10:34:20 -0700 (PDT)\r
+Date: Sat, 11 Jun 2016 17:34:18 +0000\r
+From: Gaute Hope <eg@gaute.vetsj.com>\r
+Subject: Re: [PATCH] WIP: regexp matching in 'subject' and 'from'\r
+To: Tomi Ollila <tomi.ollila@iki.fi>, David Bremner <david@tethera.net>,\r
+ Austin Clements <aclements@csail.mit.edu>\r
+Cc: notmuch <notmuch@notmuchmail.org>\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
+ <m2a8iry7nb.fsf@guru.guru-group.fi>\r
+In-Reply-To: <m2a8iry7nb.fsf@guru.guru-group.fi>\r
+User-Agent: astroid/v0.5-221-g4c2c7173 (https://github.com/gauteh/astroid)\r
+Message-Id: <1465666155-astroid-5-8srklogp6e-1296@strange>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8; format=flowed\r
+Content-Transfer-Encoding: quoted-printable\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:34:31 -0000\r
+\r
+Tomi Ollila writes on juni 11, 2016 19:09:\r
+> On Sat, Jun 11 2016, Gaute Hope <eg@gaute.vetsj.com> wrote:\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
+>=20\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
+>=20\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
+>=20\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// sla=\r
+shes/\r
+> which one could pretty easily write to the wrapper...\r
+>=20\r
+\r
+Yes, that is pretty much what I meant. So that the user only needs\r
+to know about 'search:', if it is 'search:foo' regular queryparser is\r
+used, if it is 'search:/^foo/' it is preprocessed using the regexp\r
+parser. Then the performance will remain the same for normal queries,\r
+but seamlessly switch to the heavier regexp'er if necessary.\r
+\r
+It could be done with a wrapper, but I am mainly using notmuch through\r
+the API and astroid - where it could also be implemented of course.\r
+\r
+-gaute\r
+=\r