--- /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 58676431FBF\r
+ for <notmuch@notmuchmail.org>; Sat, 25 Jan 2014 07:39:09 -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 kcCJjDjjSZgw for <notmuch@notmuchmail.org>;\r
+ Sat, 25 Jan 2014 07:39:04 -0800 (PST)\r
+Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com\r
+ [74.125.83.42]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client\r
+ certificate requested) by olra.theworths.org (Postfix) with ESMTPS id\r
+ 73840431FBC for <notmuch@notmuchmail.org>; Sat, 25 Jan 2014 07:39:04 -0800\r
+ (PST)\r
+Received: by mail-ee0-f42.google.com with SMTP id e49so1472994eek.29\r
+ for <notmuch@notmuchmail.org>; Sat, 25 Jan 2014 07:39:01 -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=0cQ2ZR2y4Z1VLclffGf+mhBxquGcDrpeJR6hyLiAgyI=;\r
+ b=jRVj3hdLTS9bHHH36DXw7NwN6lXfr5lR/PWRZQwilumROjhKYVCUdfo0zWR5HSiW6Q\r
+ KmdOcIuZDtBDKb1B7tIbTEd8mQnmkQwKVHmqew1tEQG2R3K9tSRRSJMEVIcgiLtRPf3f\r
+ NLBHoaRVLFwwYBno0CKtYGvZE1ifUFvucCUkdjFRQMUAMmGIWiJkziQYs4iaA1r1Qxv+\r
+ USdB7nOyrtQ/dsmwfmBn5ETcIP5vL8y9sJYGqDVswYATzQ/h030BFA3E3lGOmIj8/NlZ\r
+ rbMCap2LDqXUmGpLQVUnvdPaxzKTZnsUJ26v0QCYRNHfYHh727y+IMfE+MDIgb7tOirz\r
+ 9UKA==\r
+X-Gm-Message-State:\r
+ ALoCoQkLTIdLbQIxRmaIsgY5DwB/FOo4HozJEfc+DTrjagJ36UkGnESiZmzq9mKHNLDK0YSzcqcE\r
+X-Received: by 10.14.115.8 with SMTP id d8mr237167eeh.83.1390664341930;\r
+ Sat, 25 Jan 2014 07:39:01 -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 g1sm17257586eet.6.2014.01.25.07.39.00\r
+ for <multiple recipients>\r
+ (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+ Sat, 25 Jan 2014 07:39:01 -0800 (PST)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Austin Clements <aclements@csail.mit.edu>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH 0/5] lib: make folder: prefix literal\r
+In-Reply-To: <87r47wfltb.fsf@nikula.org>\r
+References: <cover.1389304779.git.jani@nikula.org>\r
+ <87y525m649.fsf@awakening.csail.mit.edu>\r
+ <87r47wfltb.fsf@nikula.org>\r
+User-Agent: Notmuch/0.17+44~ge3b4cd9 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 25 Jan 2014 17:38:59 +0200\r
+Message-ID: <87iot8f4vg.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: Sat, 25 Jan 2014 15:39:09 -0000\r
+\r
+On Sat, 25 Jan 2014, Jani Nikula <jani@nikula.org> wrote:\r
+> Perhaps we need to have two prefixes, one of which is the literal\r
+> filesystem folder and another which hides the implementation details,\r
+> like I mentioned in my mail to Peter [1]. But consider this: my proposed\r
+> implementation does cover *all* use cases.\r
+\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
+For example:\r
+\r
+folder:foo match files in foo, foo/new, and foo/cur.\r
+folder:foo/ match all files in all subdirectories under foo (this\r
+ would handle Tomi's use case), including foo/new and foo/cur.\r
+folder:foo/. match in foo only, and specifically not in foo/cur or foo/new.\r
+folder:foo/new match in foo/new, and specifically not in foo/cur (this\r
+ allows distinguishing between messages in cur and new).\r
+folder:/ match everything.\r
+folder:/. match in top level maildir only.\r
+folder:"" match in top level maildir, including cur/new.\r
+\r
+This requires indexing all the path components with suitable\r
+suffixes. For example, a file "foo/new/baz" would get terms "/", "foo",\r
+"foo/", "foo/new", and "foo/new/.". A file foo/bar would get terms "/",\r
+"foo", "foo/", and "foo/.".\r
+\r
+It's obviously a concern this increases the database size; not sure how\r
+it would compare with the current stemmed probabilistic prefix.\r
+\r
+Opinions on this? This would really cover all use cases, and address\r
+Austin's interface and backward compatibility concerns.\r
+\r
+BR,\r
+Jani.\r