On Sat, May 03 2014, dm-list-email-notm...@scs.stanford.edu wrote: > Jani Nikula <j...@nikula.org> writes: > >> On Fri, 02 May 2014, dm-list-email-notm...@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.
I use git-style segregation where mails are scattered into 256 subdirectories under a directory (based on md5hash of the mail file contents). By default mails go under received/??/. results: $ notmuch count folder:received 3 (I seem to have 3 test emails under the root of ~/.mail/received) $ notmuch count folder:received/** 0 (Apparently unsupported search ;D -- I have setopt no_nomatch in my zsh so it doesn't barf when 'folder:received/**' doesn't match anything and that saves me quoting effort :D) $ notmuch count path:received/ 0 $ notmuch count path:received 3 (again) $ notmuch count path:received/** 19439 That's probably right. Inconvenient syntax though (No, I am not complaining) > > David Tomi Lets briefly verify this... $ find ~/mail/received -type f | wc 21151 21151 1353561 Hmm $ ~/vc/projects/toomuch/check-mid-duplicates.pl mail/received | wc mail/received/00/9feb4f33523a003768a22b2f9df8f9: no Message-ID mail/received/10/10ab4e570fdd8bf744dad93d2f1c7a: no Message-ID mail/received/32/60aef86b3bf8837c1c6a8a20d5d519: no Message-ID mail/received/zap: 'from' or 'date' header missing, not a mail file ? mail/received/e1/f1be5aa84c8b28d1056aa9a8bc5b4f: no Message-ID mail/received/19/4c0e3e812721da11ad71dfe26f5b05: no Message-ID mail/received/41/d7083964e92c70ed57a3c8afd4d1d6: no Message-ID mail/received/96/22de40b7c48d3ff32101777eade693: no Message-ID mail/received/e7/8f5b883692e79627d53cf607228b02: no Message-ID mail/received/d1/248c296b7ce635848c442b4c06a9f2: no Message-ID 1711 17110 331583 Uh huh, have to check what is going on there.... _______________________________________________ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch