--- /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 8E075431FBD\r
+ for <notmuch@notmuchmail.org>; Sat, 25 Jan 2014 03:06:35 -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 ho9bmCHAYeYw for <notmuch@notmuchmail.org>;\r
+ Sat, 25 Jan 2014 03:06:30 -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
+ E3C67431FBC for <notmuch@notmuchmail.org>; Sat, 25 Jan 2014 03:06:29 -0800\r
+ (PST)\r
+Received: by mail-ee0-f42.google.com with SMTP id e49so1392670eek.29\r
+ for <notmuch@notmuchmail.org>; Sat, 25 Jan 2014 03:06:27 -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=xe5ZjDv+sUFubCOxoNmTsD0FNnEqtIMCDal5rGtuMSA=;\r
+ b=YkuzUum/coVuAl2RwESl2aKj4DVnpP7WONMqXBlDK/7qKB8fNlr+zmWggBRgqfp7gX\r
+ rXWCZsF6wOUIrFIb0EMxvJedGn7d5QKfaDS8ek+jux2OI4mryLSpxxLCecCz9SUj95fo\r
+ fpKLwdO/j1RKvTEbxO+L7p72rLw0jykdg/U6s89Xfw3xaa/QMbg/vmyT87bNImCeL+rr\r
+ ScWK6mPEvwZE8U5VzfPp5qapPb35X3EgqwllHCXsj+cIwyqVZl9+XXDq9D/VubdIwtNR\r
+ 7AWactvNdrGFvENLqXaOYMU1+U7L1Hbdw0SnBKprzg1Dr8bPxzqDyCz5L6Vr/PjhB+sQ\r
+ PWXg==\r
+X-Gm-Message-State:\r
+ ALoCoQnr9n45eiNMebLVNrSgNDu0mQtxiTeIwKJAObaCfOt1k3Vf0yAZZKSHN4rXYlSkD69Odr2p\r
+X-Received: by 10.14.0.201 with SMTP id 49mr17098412eeb.38.1390647987476;\r
+ Sat, 25 Jan 2014 03:06:27 -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 46sm14726160ees.4.2014.01.25.03.06.26\r
+ for <multiple recipients>\r
+ (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+ Sat, 25 Jan 2014 03:06:26 -0800 (PST)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Tomi Ollila <tomi.ollila@iki.fi>,\r
+ Austin Clements <aclements@csail.mit.edu>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH 0/5] lib: make folder: prefix literal\r
+In-Reply-To: <m2zjmks5hq.fsf@guru.guru-group.fi>\r
+References: <cover.1389304779.git.jani@nikula.org>\r
+ <87y525m649.fsf@awakening.csail.mit.edu>\r
+ <87r47wfltb.fsf@nikula.org> <m2zjmks5hq.fsf@guru.guru-group.fi>\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 13:06:25 +0200\r
+Message-ID: <87ob30fhhq.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 11:06:35 -0000\r
+\r
+On Sat, 25 Jan 2014, Tomi Ollila <tomi.ollila@iki.fi> wrote:\r
+> On Sat, Jan 25 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
+> I challenge that with my use case: my mails are arranged as follows: \r
+\r
+[snip]\r
+\r
+> For me the current folder: works as I don't have collisions.\r
+\r
+Fair enough, your use case would be *very inconvenient* with the\r
+proposed changes to the folder: prefix, *regardless* of whether the leaf\r
+cur/new is indexed and required or not.\r
+\r
+(Very inconvenient, or practically impossible, as you'd have to include\r
+all those 01..ff directories in your searches.)\r
+\r
+> For me a folder: search which would just work as a prefix i.e. match\r
+> anything under given directory hierarchy would work best.\r
+\r
+Indeed. Your use case is not an argument in whether cur/new should be\r
+included or not.\r
+\r
+That "recursive folder prefix" suggestion is, I think, incompatible with\r
+the requirements for the literal folder: prefix we've been considering.\r
+\r
+\r
+BR,\r
+Jani.\r
+\r