--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 46D82431E82\r
+ for <notmuch@notmuchmail.org>; Sat, 3 May 2014 11:57:37 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.502\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.502 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id CmtshuSstImd for <notmuch@notmuchmail.org>;\r
+ Sat, 3 May 2014 11:57:33 -0700 (PDT)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id D2935431E64\r
+ for <notmuch@notmuchmail.org>; Sat, 3 May 2014 11:57:32 -0700 (PDT)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1Wgf7d-0001f6-Ik; Sat, 03 May 2014 19:57:27 +0100\r
+Received: from 5751dfa2.skybroadband.com ([87.81.223.162] helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1Wgf7d-0007R8-8H; Sat, 03 May 2014 19:57:17 +0100\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: David Mazieres expires 2014-08-01 PDT\r
+ <mazieres-kdhm6yewp4dq87x4tf5ix7eyxw@temporary-address.scs.stanford.edu>,\r
+ Jani Nikula <jani@nikula.org>\r
+Subject: Re: folder and path completely broken in HEAD?\r
+In-Reply-To: <87iopmonzn.fsf@ta.scs.stanford.edu>\r
+References: <87oazfo3w2.fsf@ta.scs.stanford.edu> <87zjiz8hft.fsf@qmul.ac.uk>\r
+ <87iopmonzn.fsf@ta.scs.stanford.edu>\r
+User-Agent: Notmuch/0.15.2+615~g78e3a93 (http://notmuchmail.org) Emacs/23.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 03 May 2014 19:57:15 +0100\r
+Message-ID: <87ppju4rn8.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Sender-Host-Address: 87.81.223.162\r
+X-QM-Geographic: According to ripencc,\r
+ this message was delivered by a machine in Britain (UK) (GB).\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: 2b402357401b55cb326276c6e6662c14 (of first 20000 bytes)\r
+X-SpamAssassin-Score: -0.1\r
+X-SpamAssassin-SpamBar: /\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored -0.1 points.\r
+ Summary of the scoring: \r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * -0.1 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 03 May 2014 18:57:37 -0000\r
+\r
+\r
+Hi\r
+\r
+On Sat, 03 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:\r
+> Mark Walters <markwalters1009@gmail.com> writes:\r
+>\r
+>>> All the way back. Now you are saying there will be no convenient way to\r
+>>> match just the "mail.class" part without the year? How very\r
+>>> distressing. Ugh.\r
+>>\r
+>> Hi\r
+>>\r
+>> I am not quite sure what you are meaning by hierarchically group\r
+>> messages. Searching for path:dir/foo/bar/** should give all messages in\r
+>> all directories beneath dir/foo/bar. \r
+>\r
+> The problem is that the maildir++ spec disallows such pathnames. If I\r
+> need compatibility with maildir++ (for instance for an imap server), at\r
+> least on a per-year basis, then my maildirs have to have names like:\r
+>\r
+> 2013/.foo.foo\r
+> 2013/.foo.bar\r
+> 2013/.foo.baz\r
+> 2014/.foo.foo\r
+> 2014/.foo.bar\r
+> 2014/.foo.baz\r
+>\r
+> So if I want a way to aggregate all my foo mail in a single search,\r
+> right now I just ask for folder:foo. Will there be any equivalent in\r
+> the new notmuch?\r
+\r
+I agree with Jani that for 0.18 this won't be possible. However, there\r
+is probably no urgent reason to upgrade (given you know it will cause\r
+you some problems) so the question is can we add some functionality to\r
+cover this use case. Given the way we do the folder matching I think it\r
+unlikely we would want to add globbing/wildcards to the start of a path\r
+(*).\r
+\r
+However, we might be able to support maildir++ as its own prefix. If you\r
+could so searches of the form maildir++:.foo.bar.** which would match\r
+the maildir .foo.bar and all submaildirs++ (eg .foo.bar.a.b etc) would\r
+that be sufficient?\r
+\r
+This wouldn't deal with 2013/.foo.bar but would allow .foo.bar.2013\r
+\r
+Would this be enough help to make it worth considering?\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+(*) if we get a custom parser then it may all be manageable.\r
+\r
projects / notmuch-archives.git / commitdiff