unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jani Nikula <jani@nikula.org>
To: David Mazieres expires 2014-07-31 PDT
	<mazieres-zk7gikin52b3hgy9ybcegjvvmi@temporary-address.scs.stanford.edu>,
	notmuch@notmuchmail.org
Subject: Re: folder and path completely broken in HEAD?
Date: Sat, 03 May 2014 00:29:27 +0300	[thread overview]
Message-ID: <87zjizyimg.fsf@nikula.org> (raw)
In-Reply-To: <87tx98xel7.fsf@ta.scs.stanford.edu>

On Fri, 02 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:
> Hey, I'm playing around with the head of the git repository
> (bc64cdce289d84be2550c4fccb1f008d15eaeb0e) to try to figure out how the
> new folder: prefixes work, as folders are a critical part of how I
> organize my mail.  (Since tags are not hierarchical, folders are the
> best way for me to group mail to a bunch of related addresses, while
> retaining the ability to separate out any mailboxes that become high
> traffic.)
>
> I'm using a pretty standard maildir++ layout.  For example, underneath
> my database.path I have a bunch of mail in directories such as:
>
>     .INBOX.Main/{new,cur}
>     .mail.class/{new,cur}
>     .mail.voicemail/{new,cur}
>
> It used to be the case that if I wanted to read all of my "mail" mail, I
> could search for folder:mail, while to look at just voicemail, I could
> say folder:mail.voicemail, etc.  Now, I can't get anything to match a
> folder predicate period.  For example, using notmuch as notmuch-0.17 and
> ./notmuch as notmuch-0.18-rc2+2~gbc64cdc, here's what I get:

First, read Mark's reply about database upgrade, and heed the notice
about upgrade being automatic but downgrade requiring a reindex of all
your mails.

Here's additional commentary on the specific queries.

>         linux7$ ./notmuch count folder:mail
>         0
>         linux8$ ./notmuch count folder:.mail
>         0

These two will not match anything.

>         linux9$ ./notmuch count folder:.mail.voicemail
>         0

After the upgrade, this should work for .mail.voicemail/{new,cur}.

>         linux10$ ./notmuch count folder:.mail.voicemail/cur
>         0

This won't match anything. To specifically search for messages in cur,
you can use the new path prefix, path:.mail.voicemail/cur

>         linux 11$ ./notmuch count path:.mail.voicemail
>         0

This will match messages in .mail.voicemail only, and nothing in the cur
or new subdirectories.

>         linux 12$ ./notmuch count path:.mail.voicemail/'**'
>         0

I'm not sure your quoting will work, but if you don't have any other
subfolders than cur and new, this should be equal to
folder:.mail.voicemail

>         linux 13$ ./notmuch count path:.mail.voicemail/cur 
>         0

This should match messages in the cur subdirectory.

>         linux 14$ ./notmuch count folder:mail.voicemail
>         0

This won't match anything.


BR,
Jani.

  parent reply	other threads:[~2014-05-02 21:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 17:41 folder and path completely broken in HEAD? dm-list-email-notmuch
2014-05-02 18:10 ` Mark Walters
2014-05-02 21:16   ` David Mazieres expires 2014-07-31 PDT
2014-05-03  5:44     ` Suvayu Ali
2014-05-02 21:29 ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-03  4:57 dm-list-email-notmuch
2014-05-03  5:49 ` Suvayu Ali
2014-05-03  7:11 ` Mark Walters
2014-05-03 15:55   ` dm-list-email-notmuch
2014-05-03 17:53     ` Jani Nikula
2014-05-04  1:34       ` dm-list-email-notmuch
     [not found]         ` <87mwewkjzu.fsf@yoom.home.cworth.org>
2014-05-05 22:34           ` Jani Nikula
2014-05-06  7:44             ` Mark Walters
     [not found]               ` <87eh06jngf.fsf@yoom.home.cworth.org>
2014-05-07 19:24                 ` Mark Walters
2014-05-09 20:01         ` Jameson Graef Rollins
2014-05-03 18:57     ` Mark Walters
2014-05-03  7:29 ` Tomi Ollila

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zjizyimg.fsf@nikula.org \
    --to=jani@nikula.org \
    --cc=mazieres-zk7gikin52b3hgy9ybcegjvvmi@temporary-address.scs.stanford.edu \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).