From: Mark Walters Date: Sat, 3 May 2014 07:11:50 +0000 (+0100) Subject: Re: folder and path completely broken in HEAD? X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=2a3472993f7b13de03163888e063f70ff531645c;p=notmuch-archives.git Re: folder and path completely broken in HEAD? --- diff --git a/d3/0ef698ef057148c17457c51c4c14e656aa2183 b/d3/0ef698ef057148c17457c51c4c14e656aa2183 new file mode 100644 index 000000000..4d06394ba --- /dev/null +++ b/d3/0ef698ef057148c17457c51c4c14e656aa2183 @@ -0,0 +1,152 @@ +Return-Path: +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 1DD1C431E82 + for ; Sat, 3 May 2014 00:12:09 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 0.502 +X-Spam-Level: +X-Spam-Status: No, score=0.502 tagged_above=-999 required=5 + tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, + NML_ADSP_CUSTOM_MED=1.2, 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 mcFlvcYeaDTN for ; + Sat, 3 May 2014 00:12:01 -0700 (PDT) +Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6]) + (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id C1740431E62 + for ; Sat, 3 May 2014 00:12:00 -0700 (PDT) +Received: from smtp.qmul.ac.uk ([138.37.6.40]) + by mail2.qmul.ac.uk with esmtp (Exim 4.71) + (envelope-from ) + id 1WgU6x-00035V-Pz; Sat, 03 May 2014 08:11:55 +0100 +Received: from 5751dfa2.skybroadband.com ([87.81.223.162] helo=localhost) + by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71) + (envelope-from ) + id 1WgU6x-0004q8-Fb; Sat, 03 May 2014 08:11:51 +0100 +From: Mark Walters +To: David Mazieres expires 2014-07-31 PDT + , + Jani Nikula +Subject: Re: folder and path completely broken in HEAD? +In-Reply-To: <87oazfo3w2.fsf@ta.scs.stanford.edu> +References: <87oazfo3w2.fsf@ta.scs.stanford.edu> +User-Agent: Notmuch/0.15.2+615~g78e3a93 (http://notmuchmail.org) Emacs/23.4.1 + (x86_64-pc-linux-gnu) +Date: Sat, 03 May 2014 08:11:50 +0100 +Message-ID: <87zjiz8hft.fsf@qmul.ac.uk> +MIME-Version: 1.0 +Content-Type: text/plain; charset=us-ascii +X-Sender-Host-Address: 87.81.223.162 +X-QM-Geographic: According to ripencc, + this message was delivered by a machine in Britain (UK) (GB). +X-QM-SPAM-Info: Sender has good ham record. :) +X-QM-Body-MD5: 7129430a0d3ec8ecc226dc40ce18c7d8 (of first 20000 bytes) +X-SpamAssassin-Score: -0.1 +X-SpamAssassin-SpamBar: / +X-SpamAssassin-Report: The QM spam filters have analysed this message to + determine if it is + spam. We require at least 5.0 points to mark a message as spam. + This message scored -0.1 points. + Summary of the scoring: + * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail + provider * (markwalters1009[at]gmail.com) + * -0.1 AWL AWL: From: address is in the auto white-list +X-QM-Scan-Virus: ClamAV says the message is clean +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." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Sat, 03 May 2014 07:12:09 -0000 + + +On Sat, 03 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote: +> Jani Nikula 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. + +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. + +So for the year example you give you could have directories +mail/class/2013 and mail/class/2014/ etc. + +Anyway if you can describe your use more fully we may be able to +help. And if it can't do what you want it would also give us some idea +of what would need to be changed. + +Finally, I am not quite sure what this means + +> 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. + +Are you wanting to tag messages based on some properties when doing +notmuch new while avoiding races etc? Or are you worried about duplicate +message-ids? Or something else? + +Best wishes + +Mark + + + + +> +> David +> _______________________________________________ +> notmuch mailing list +> notmuch@notmuchmail.org +> http://notmuchmail.org/mailman/listinfo/notmuch