--- /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 25E73431E82\r
+ for <notmuch@notmuchmail.org>; Fri, 2 May 2014 11:10:39 -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 1MOpBU+JWAU6 for <notmuch@notmuchmail.org>;\r
+ Fri, 2 May 2014 11:10:31 -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 6C1A2431FC2\r
+ for <notmuch@notmuchmail.org>; Fri, 2 May 2014 11:10:31 -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 1WgHuZ-0002XA-4Z; Fri, 02 May 2014 19:10:26 +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 1WgHuY-00060f-QO; Fri, 02 May 2014 19:10:15 +0100\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: David Mazieres expires 2014-07-31 PDT\r
+ <mazieres-zk7gikin52b3hgy9ybcegjvvmi@temporary-address.scs.stanford.edu>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: folder and path completely broken in HEAD?\r
+In-Reply-To: <87tx98xel7.fsf@ta.scs.stanford.edu>\r
+References: <87tx98xel7.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: Fri, 02 May 2014 19:10:13 +0100\r
+Message-ID: <87k3a49hmi.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: adda03b88f1e1ba0c98ccb7ec83275ec (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
+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: Fri, 02 May 2014 18:10:39 -0000\r
+\r
+\r
+Hi\r
+\r
+Before checking other things: have you run notmuch new? That's needed to\r
+update the database. It is an irreversible update so notmuch-0.17 will\r
+not work with the updated database.\r
+\r
+The update should save a dump of the tags before updating but you might\r
+want to do that manually too (and maybe even keep a complete copy of the\r
+database). The update might take quite a long time (but it can be\r
+interrupted and restarted)\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
+On Fri, 02 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:\r
+> Hey, I'm playing around with the head of the git repository\r
+> (bc64cdce289d84be2550c4fccb1f008d15eaeb0e) to try to figure out how the\r
+> new folder: prefixes work, as folders are a critical part of how I\r
+> organize my mail. (Since tags are not hierarchical, folders are the\r
+> best way for me to group mail to a bunch of related addresses, while\r
+> retaining the ability to separate out any mailboxes that become high\r
+> traffic.)\r
+>\r
+> I'm using a pretty standard maildir++ layout. For example, underneath\r
+> my database.path I have a bunch of mail in directories such as:\r
+>\r
+> .INBOX.Main/{new,cur}\r
+> .mail.class/{new,cur}\r
+> .mail.voicemail/{new,cur}\r
+>\r
+> It used to be the case that if I wanted to read all of my "mail" mail, I\r
+> could search for folder:mail, while to look at just voicemail, I could\r
+> say folder:mail.voicemail, etc. Now, I can't get anything to match a\r
+> folder predicate period. For example, using notmuch as notmuch-0.17 and\r
+> ./notmuch as notmuch-0.18-rc2+2~gbc64cdc, here's what I get:\r
+>\r
+> linux2$ notmuch count folder:mail\r
+> 16257\r
+> linux3$ notmuch count folder:mail.class\r
+> 1896\r
+> linux4$ notmuch count folder:mail.voicemail\r
+> 34\r
+> linux5$ notmuch count folder:mail.voicemail/cur\r
+> 34\r
+> linux6$ notmuch count folder:.mail.voicemail/cur\r
+> 34\r
+> linux7$ ./notmuch count folder:mail\r
+> 0\r
+> linux8$ ./notmuch count folder:.mail\r
+> 0\r
+> linux9$ ./notmuch count folder:.mail.voicemail\r
+> 0\r
+> linux10$ ./notmuch count folder:.mail.voicemail/cur\r
+> 0\r
+> linux 11$ ./notmuch count path:.mail.voicemail\r
+> 0\r
+> linux 12$ ./notmuch count path:.mail.voicemail/'**'\r
+> 0\r
+> linux 13$ ./notmuch count path:.mail.voicemail/cur \r
+> 0\r
+> linux 14$ ./notmuch count folder:mail.voicemail\r
+> 0\r
+>\r
+> What gives? Are the path and folder predicates completely broken, or is\r
+> something very important missing from the new notmuch-search-terms\r
+> manual page? How can I make this work?\r
+>\r
+> Thanks,\r
+> David\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
projects / notmuch-archives.git / commitdiff