unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: dm-list-email-notmuch@scs.stanford.edu
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: folder and path completely broken in HEAD?
Date: Fri, 02 May 2014 21:57:49 -0700	[thread overview]
Message-ID: <87oazfo3w2.fsf@ta.scs.stanford.edu> (raw)

Jani Nikula <jani@nikula.org> writes:

> On Fri, 02 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:
>>
>> 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}
>> ...
> Here's additional commentary on the specific queries.
>
>>         linux7$ ./notmuch count folder:mail
>>         0
>>         linux8$ ./notmuch count folder:.mail
>>         0

Oh, man.  That's a serious bummer.

Is there any mechanism left that would let me hierarchically group
messages?  I've got a ton of mail.* folders, and create new ones
dynamically.  I really want a mechanism to group them hierarchically, so
I can have a search that matches all current and future mail
directories.  I organized my whole mail setup around folders because a)
tags do not provide this kind of hierarchical control, and b) there
doesn't seem to be a convenient way to apply tags 100% reliably on
message delivery, whereas I *can* control the folder 100% reliably.

Worse, because of my poor performance, I was hoping to segregate
messages by year.  So it would be:

  2013/.mail.class
  2013/.mail.voicemail
  2014/.mail.class
  2014/.mail.voicemail

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.

David

             reply	other threads:[~2014-05-03  4:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03  4:57 dm-list-email-notmuch [this message]
2014-05-03  5:49 ` folder and path completely broken in HEAD? 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
  -- strict thread matches above, loose matches on Subject: below --
2014-05-02 17:41 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

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=87oazfo3w2.fsf@ta.scs.stanford.edu \
    --to=dm-list-email-notmuch@scs.stanford.edu \
    --cc=jani@nikula.org \
    --cc=mazieres-dznikihr9t4gcgb72gnhf9954a@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).