Message-ID: <1411396931.1931.91.camel@picnicpark.org>
Subject: Re: Do path: searches handle spaces correctly?
From: Keith Amidon <camalot@picnicpark.org>
To: David Bremner <david@tethera.net>
Date: Mon, 22 Sep 2014 07:42:11 -0700
In-Reply-To: <87tx40ggf1.fsf@maritornes.cs.unb.ca>
References: <878uleklvt.fsf@awakenetworks.com>
	<87tx40ggf1.fsf@maritornes.cs.unb.ca>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: notmuch@notmuchmail.org
Precedence: list

On Mon, 2014-09-22 at 11:20 +0200, David Bremner wrote:
> Keith Amidon <keith@awakenetworks.com> writes:
> >
> > notmuch search --output=files path:'dir/INBOX/INBOX/Sent Items'
> >
> > I don't get any results, but it seems like the two results above should
> > be shown, right?  Am I doing something wrong here?  If it looks like I'm
> > doing it correctly, what can I do to help troubleshoot the issue?
> 
> Note that path:, unlike folder:, does not add the maildir subdirs. Dunno
> if that's the only issue you are having, but I guess it's one.

Darn it!  I made a mistake in my original email.  In the test I was
doing I actually had:

notmuch search --output=files path:'dir/INBOX/INBOX/Sent Items/**'

which I believe should have picked up all the subdirectory paths.  I
just retested to make sure that it still didn't work, and it doesn't.

Am I still missing something?   Thanks for the help, Keith