1 Return-Path: <david@tethera.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by arlo.cworth.org (Postfix) with ESMTP id D95706DE01C2
\r
6 for <notmuch@notmuchmail.org>; Sat, 11 Jun 2016 09:49:53 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5
\r
12 tests=[AWL=-0.000, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]
\r
14 Received: from arlo.cworth.org ([127.0.0.1])
\r
15 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id s3m1hhp-QBJV for <notmuch@notmuchmail.org>;
\r
17 Sat, 11 Jun 2016 09:49:45 -0700 (PDT)
\r
18 Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])
\r
19 by arlo.cworth.org (Postfix) with ESMTPS id D21266DE01BE
\r
20 for <notmuch@notmuchmail.org>; Sat, 11 Jun 2016 09:49:44 -0700 (PDT)
\r
21 Received: from remotemail by fethera.tethera.net with local (Exim 4.84)
\r
22 (envelope-from <david@tethera.net>)
\r
23 id 1bBm6C-0005cC-4P; Sat, 11 Jun 2016 12:49:28 -0400
\r
24 Received: (nullmailer pid 30618 invoked by uid 1000);
\r
25 Sat, 11 Jun 2016 16:49:39 -0000
\r
26 From: David Bremner <david@tethera.net>
\r
27 To: Gaute Hope <eg@gaute.vetsj.com>, Austin Clements <aclements@csail.mit.edu>
\r
28 Cc: notmuch <notmuch@notmuchmail.org>
\r
29 Subject: Re: [PATCH] WIP: regexp matching in 'subject' and 'from'
\r
30 In-Reply-To: <1465662533-astroid-3-6vuqm3zu54-1296@strange>
\r
31 References: <1465265149-7174-1-git-send-email-david@tethera.net>
\r
32 <1465525688-30913-1-git-send-email-david@tethera.net>
\r
33 <1465547660-astroid-0-nudmv20lbk-1296@strange>
\r
34 <87a8itxpu7.fsf@zancas.localnet>
\r
35 <1465662533-astroid-3-6vuqm3zu54-1296@strange>
\r
36 User-Agent: Notmuch/0.22+28~gb9bf3f4 (http://notmuchmail.org) Emacs/24.5.1
\r
37 (x86_64-pc-linux-gnu)
\r
38 Date: Sat, 11 Jun 2016 13:49:39 -0300
\r
39 Message-ID: <87fusjvffg.fsf@zancas.localnet>
\r
41 Content-Type: text/plain
\r
42 X-BeenThere: notmuch@notmuchmail.org
\r
43 X-Mailman-Version: 2.1.20
\r
45 List-Id: "Use and development of the notmuch mail system."
\r
46 <notmuch.notmuchmail.org>
\r
47 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
49 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
50 List-Post: <mailto:notmuch@notmuchmail.org>
\r
51 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
52 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
54 X-List-Received-Date: Sat, 11 Jun 2016 16:49:54 -0000
\r
56 Gaute Hope <eg@gaute.vetsj.com> writes:
\r
59 > Maybe we could check if the search string contains a regexp and decide
\r
60 > whether to pre-process it on the background of that? I think that would
\r
61 > make the interface more user-friendly. You'd just always use search
\r
62 > whether you decide that you need to put in some regexp or not.
\r
65 There are some technical limitations of the xapian query parser (and
\r
66 field processors in particular) that mean we'll probably have explicitly
\r
67 ask for regex expansion.
\r
69 > I would rather have double the db and be able wildcard beginning of
\r
70 > terms. If it is not too much maintaining overhead it might be made
\r
73 perhaps. If that's really your primary goal, regexp search is
\r
74 overkill. Maybe you should discuss with xapian upstream the possibility
\r
75 of having xapian support more general wildcards. I have a vague memory
\r
76 of olly once saying it was not out of the question. But I might be wrong
\r
77 about that, it's just a half-remembered IRC discussion.
\r