Return-Path: <jani@nikula.org>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 19020431E64
	for <notmuch@notmuchmail.org>; Sat,  3 May 2014 10:53:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
	tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HOnUktxZ7PAG for <notmuch@notmuchmail.org>;
	Sat,  3 May 2014 10:53:20 -0700 (PDT)
Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com
 [74.125.83.47])	(using TLSv1 with cipher RC4-SHA (128/128 bits))	(No client
 certificate requested)	by olra.theworths.org (Postfix) with ESMTPS id
 BE75C431FDA	for <notmuch@notmuchmail.org>; Sat,  3 May 2014 10:53:19 -0700
 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id b15so4060197eek.6
	for <notmuch@notmuchmail.org>; Sat, 03 May 2014 10:53:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:from:to:cc:subject:in-reply-to:references
	:user-agent:date:message-id:mime-version:content-type;
	bh=p9tnXEOe+yxqkS7HlJkhJq6TqkpwxfyM4XqmWykL0wE=;
	b=gQjzW4Shm+UhjjFWDidJ8vUw4N5R5bXHUUczpq+4jVEutlD8oONL/8nI3YGSQ851At
	SN9AGeScWzbojkNYWWq5i6iVt5Fu64gJtDLKmUeqEGeUT/SDthqlu6athFT0JbEglXM5
	w14kLXMzXXYg8ebxOi4GyOSTAmIyiCO1W5MsS5XCtXknpLmnisrWVNtiaUT2bwhdW1nS
	JfN+i6jnR+Qtfa8zKAtzxg/1pOpqDQTwV+N2nCJm8QTqNxCnCk57GoLwwLlZLF10VKfZ
	CgZI0QeM1o/1ctZT2JEjOQ5pGcCm3m+y2uggDUTK5Sa5zey6TdROciqylS6D6pWhHjeh
	tGEw==
X-Gm-Message-State:
 ALoCoQklTyKDr5dsz8bVwSqaue4wO0vzEMBhySlSZ6cjjWxDautXhffEksSenvTi1fKTysDl/e5e
X-Received: by 10.14.115.1 with SMTP id d1mr21658798eeh.30.1399139596169;
	Sat, 03 May 2014 10:53:16 -0700 (PDT)
Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi.
	[88.195.111.91])
	by mx.google.com with ESMTPSA id u46sm14495808eel.1.2014.05.03.10.53.14
	for <multiple recipients>
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Sat, 03 May 2014 10:53:15 -0700 (PDT)
From: Jani Nikula <jani@nikula.org>
To: David Mazieres expires 2014-08-01 PDT
	<mazieres-kdhm6yewp4dq87x4tf5ix7eyxw@temporary-address.scs.stanford.edu>,
	Mark Walters <markwalters1009@gmail.com>
Subject: Re: folder and path completely broken in HEAD?
In-Reply-To: <87iopmonzn.fsf@ta.scs.stanford.edu>
References: <87oazfo3w2.fsf@ta.scs.stanford.edu> <87zjiz8hft.fsf@qmul.ac.uk>
	<87iopmonzn.fsf@ta.scs.stanford.edu>
User-Agent: Notmuch/0.18~rc0+2~gbc64cdc (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-pc-linux-gnu)
Date: Sat, 03 May 2014 20:53:13 +0300
Message-ID: <87tx96ycja.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain
Cc: notmuch@notmuchmail.org
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Sat, 03 May 2014 17:53:24 -0000

On Sat, 03 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:
> Mark Walters <markwalters1009@gmail.com> writes:
>
>>> All the way back.  Now you are saying there will be no convenient way to
>>> match just the "mail.class" part without the year?  How very
>>> distressing.  Ugh.
>>
>> Hi
>>
>> I am not quite sure what you are meaning by hierarchically group
>> messages. Searching for path:dir/foo/bar/** should give all messages in
>> all directories beneath dir/foo/bar. 
>
> The problem is that the maildir++ spec disallows such pathnames.  If I
> need compatibility with maildir++ (for instance for an imap server), at
> least on a per-year basis, then my maildirs have to have names like:
>
>    2013/.foo.foo
>    2013/.foo.bar
>    2013/.foo.baz
>    2014/.foo.foo
>    2014/.foo.bar
>    2014/.foo.baz
>
> So if I want a way to aggregate all my foo mail in a single search,
> right now I just ask for folder:foo.  Will there be any equivalent in
> the new notmuch?

Given that we're in feature freeze and ready for an imminent release of
0.18, I think it's pretty safe to say, no.

---

It's not going to help you, but I'll mention a few of the issues the old
folder: search had, which we also had complaints about, and which would
have been quite hard to fix while preserving the behaviour you want. In
short, we considered the old folder: search broken.

Given layout:

	Foo/{cur,new}
	foo/{cur,new}
	fooing/{cur,new}
	bar/foo/{cur,new}
	cur
	new

It was impossible to refer to the top level folder.

It was impossible to refer to foo without also referring to Foo, fooing,
and bar/foo.

In your layout, if you also had 2013/.bar.foo, folder:foo would match
that as well. To not match that, you would have to include each
folder:.foo.xxx in the search.


BR,
Jani.