From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id D95706DE01C2 for ; Sat, 11 Jun 2016 09:49:53 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.011 X-Spam-Level: X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 s3m1hhp-QBJV for ; Sat, 11 Jun 2016 09:49:45 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id D21266DE01BE for ; Sat, 11 Jun 2016 09:49:44 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1bBm6C-0005cC-4P; Sat, 11 Jun 2016 12:49:28 -0400 Received: (nullmailer pid 30618 invoked by uid 1000); Sat, 11 Jun 2016 16:49:39 -0000 From: David Bremner To: Gaute Hope , Austin Clements Cc: notmuch Subject: Re: [PATCH] WIP: regexp matching in 'subject' and 'from' In-Reply-To: <1465662533-astroid-3-6vuqm3zu54-1296@strange> References: <1465265149-7174-1-git-send-email-david@tethera.net> <1465525688-30913-1-git-send-email-david@tethera.net> <1465547660-astroid-0-nudmv20lbk-1296@strange> <87a8itxpu7.fsf@zancas.localnet> <1465662533-astroid-3-6vuqm3zu54-1296@strange> User-Agent: Notmuch/0.22+28~gb9bf3f4 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Sat, 11 Jun 2016 13:49:39 -0300 Message-ID: <87fusjvffg.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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2016 16:49:54 -0000 Gaute Hope writes: > > Maybe we could check if the search string contains a regexp and decide > whether to pre-process it on the background of that? I think that would > make the interface more user-friendly. You'd just always use search > whether you decide that you need to put in some regexp or not. > There are some technical limitations of the xapian query parser (and field processors in particular) that mean we'll probably have explicitly ask for regex expansion. > I would rather have double the db and be able wildcard beginning of > terms. If it is not too much maintaining overhead it might be made > optional? perhaps. If that's really your primary goal, regexp search is overkill. Maybe you should discuss with xapian upstream the possibility of having xapian support more general wildcards. I have a vague memory of olly once saying it was not out of the question. But I might be wrong about that, it's just a half-remembered IRC discussion. d