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