--- /dev/null
+Return-Path: <jani@nikula.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 87C22431FBF\r
+ for <notmuch@notmuchmail.org>; Wed, 29 Jan 2014 11:05:46 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id jdHG4c6S51KY for <notmuch@notmuchmail.org>;\r
+ Wed, 29 Jan 2014 11:05:37 -0800 (PST)\r
+Received: from mail-ea0-f179.google.com (mail-ea0-f179.google.com\r
+ [209.85.215.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 45D7D431FBD\r
+ for <notmuch@notmuchmail.org>; Wed, 29 Jan 2014 11:05:37 -0800 (PST)\r
+Received: by mail-ea0-f179.google.com with SMTP id q10so941042ead.24\r
+ for <notmuch@notmuchmail.org>; Wed, 29 Jan 2014 11:05:34 -0800 (PST)\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:from:to:subject:in-reply-to:references\r
+ :user-agent:date:message-id:mime-version:content-type;\r
+ bh=ruJSi2DoWO7Z83uIA1BRpmJdAFm2S77i5UIHbdMn+II=;\r
+ b=Ieye9qTsbW6SPdUsPu4MpS/ibwHdVCCzEdWaj8A9wuiqHntT+YhroHJEjn61XaR5qf\r
+ B6JuYmVuh/93NsyBYM9bW6qeWwrERQi8eWes1Kfug++A0/9J9uBiC/ZvtvdI6aeygR0Z\r
+ xbC/fBxzhYcNNrdlyJPMBrFNEQJyr9uAFy+TeaXDmXSPEgWMc1k3y1sM0CBgCHG76iL2\r
+ p+BCP4etSqzbUiet4CEFN5Qdcgl2rNAclIJDiScT5mfZWbqtchE4DHpgtQA2sDCkpdMw\r
+ zPoFVF5nLoYh3Y4/13pYlk2IvxsHrRF7fLbmnzbBziHH4e5vgHVxK+xz7L1QDbIp5ypb\r
+ EqDA==\r
+X-Gm-Message-State:\r
+ ALoCoQmQwlRs051nC/uX5gx8uhesp8aluvZlalxEqTrAmDaJ00mNFORPKS01BXjHaKKJL9BVdc/M\r
+X-Received: by 10.15.36.65 with SMTP id h41mr11808769eev.0.1391022334730;\r
+ Wed, 29 Jan 2014 11:05:34 -0800 (PST)\r
+Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi.\r
+ [88.195.111.91])\r
+ by mx.google.com with ESMTPSA id k6sm12426881eep.17.2014.01.29.11.05.31\r
+ for <multiple recipients>\r
+ (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+ Wed, 29 Jan 2014 11:05:33 -0800 (PST)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Carl Worth <cworth@cworth.org>, Austin Clements <aclements@csail.mit.edu>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: [PATCH 0/5] lib: make folder: prefix literal\r
+In-Reply-To: <874n4rvcvo.fsf@yoom.home.cworth.org>\r
+References: <cover.1389304779.git.jani@nikula.org>\r
+ <87y525m649.fsf@awakening.csail.mit.edu>\r
+ <87r47wfltb.fsf@nikula.org> <87iot8f4vg.fsf@nikula.org>\r
+ <874n4rvcvo.fsf@yoom.home.cworth.org>\r
+User-Agent: Notmuch/0.17+44~ge3b4cd9 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Wed, 29 Jan 2014 21:05:30 +0200\r
+Message-ID: <874n4mfw1x.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://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: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 29 Jan 2014 19:05:46 -0000\r
+\r
+On Sun, 26 Jan 2014, Carl Worth <cworth@cworth.org> wrote:\r
+> Jani Nikula <jani@nikula.org> writes:\r
+>> Here's a thought. With boolean prefix folder:, we can devise a scheme\r
+>> where the folder: query defines what is to be matched.\r
+>\r
+> I like the idea, but I tried to infer the rules from the examples, and I\r
+> failed. It looks like there are two new symbols, "/" and "/." but I\r
+> couldn't decipher the exact semantics of each.\r
+>\r
+> I think a proposal like this should not re-use the '/' symbol as we\r
+> already have that as a path divider. (See rsync for lots of user\r
+> confusion with a significant trailing '/').\r
+>\r
+> I propose a similar, but slightly different approach, where we add two\r
+> additional symbols:\r
+>\r
+> '^' Matches the beginning of a path\r
+>\r
+> '$' Matches the end of a path\r
+>\r
+> [Obviously, I chose these symbols from regular expressions. I would be\r
+> OK with alternate symbols, ('$' seems like it might be problematic in\r
+> the shell, but perhaps not too much if it's always at the end of a\r
+> phrase.)]\r
+>\r
+> This way, one could search for:\r
+>\r
+> folder:foo Works like "folder:" historically\r
+>\r
+> folder:^full/path$ Works like Jani's proposal\r
+>\r
+> folder:^path/prefix Satisfies Tomi's use case, (as well as anyone\r
+> who doesn't want to have to specify or\r
+> distinguish between "/cur" or "/new".\r
+>\r
+> Any extra '/' at the beginning or end of a search string, (such as\r
+> "folder:^/full/path/$") would not change the semantics.\r
+>\r
+> Further, I think we can implement this with less database bloat by\r
+> leaving "folder" as probabilistic and simply indexing two new terms to\r
+> indicate the beginning of the path and the end of the path.\r
+>\r
+> Finally, we could also extend the scheme to other things like subject:\r
+> to allow for an exact subject search like:\r
+>\r
+> "subject:^lib: make folder: prefix literal$"\r
+>\r
+> It was with an eye toward something like this that I chose to make\r
+> folder: probabilistic in the first place. (I probably would have indexed\r
+> things appropriately in the first place as well, but at the time doing\r
+> the necessary query parsing for '^' and '$' seemed daunting).\r
+\r
+Unfortunately, I haven't had the time to experiment with this. But it\r
+bugs me that the probabilistic folder: prefix has stemming and it's case\r
+insensitive. It's possible to work around the stemming with the anchors\r
+you suggest or by quoting, but is there a way to have case sensitive\r
+probabilistic prefixes?\r
+\r
+BR,\r
+Jani.\r
projects / notmuch-archives.git / commitdiff