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 EADF86DE0C81 for ; Sun, 5 Feb 2017 15:28:42 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.005 X-Spam-Level: X-Spam-Status: No, score=-0.005 tagged_above=-999 required=5 tests=[AWL=0.006, 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 rcnkNbzqZhAd for ; Sun, 5 Feb 2017 15:28:41 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 751A86DE1290 for ; Sun, 5 Feb 2017 15:28:41 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1caWE0-0004NJ-B9; Sun, 05 Feb 2017 18:28:04 -0500 Received: (nullmailer pid 13562 invoked by uid 1000); Sun, 05 Feb 2017 23:28:35 -0000 From: David Bremner To: Tomi Ollila , notmuch@notmuchmail.org Subject: Re: [Patch v4] lib: regexp matching in 'subject' and 'from' In-Reply-To: References: <20170121032752.6788-1-david@tethera.net> <20170121135917.22062-1-david@tethera.net> <87efzqef2r.fsf@tethera.net> <87ziia2jpj.fsf@nikula.org> Date: Sun, 05 Feb 2017 19:28:35 -0400 Message-ID: <87shns8bfg.fsf@rocinante.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Sun, 05 Feb 2017 23:28:43 -0000 Tomi Ollila writes: > TOn Sun, Jan 29 2017, Jani Nikula wrote: > >> >> I'd go with an error. It's easy to loosen the rules later on if we >> decide that's a good idea. Much harder to accept loose rules now, let >> users get used to it, and try to tighten the rules if we realize we'd >> need that for some reason. > > I agree -- should we allow trailing slash ('/') without first char also > being '/' (e.g. subject:blah/) > I'd say that should also be an error. it doesn't add anything useful to subject search. Even for path search, (which is non-trivial to add regex search for, I think) the trailing / doesn't add anything does it? d