From 9944dccf190e42f52ea6f5106ff9617e4adb891a Mon Sep 17 00:00:00 2001 From: Jani Nikula Date: Sat, 3 May 2014 00:29:27 +0300 Subject: [PATCH] Re: folder and path completely broken in HEAD? --- 44/1df37d9ddb60de43f58461e5d1410893714092 | 144 ++++++++++++++++++++++ 1 file changed, 144 insertions(+) create mode 100644 44/1df37d9ddb60de43f58461e5d1410893714092 diff --git a/44/1df37d9ddb60de43f58461e5d1410893714092 b/44/1df37d9ddb60de43f58461e5d1410893714092 new file mode 100644 index 000000000..96c07801d --- /dev/null +++ b/44/1df37d9ddb60de43f58461e5d1410893714092 @@ -0,0 +1,144 @@ +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 4D9B3429E2F + for ; Fri, 2 May 2014 14:29:38 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.7 +X-Spam-Level: +X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 + tests=[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 JFhWVV8q0UGU for ; + Fri, 2 May 2014 14:29:30 -0700 (PDT) +Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com + [74.125.83.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client + certificate requested) by olra.theworths.org (Postfix) with ESMTPS id + A02F4431FC2 for ; Fri, 2 May 2014 14:29:30 -0700 + (PDT) +Received: by mail-ee0-f44.google.com with SMTP id c41so3431145eek.17 + for ; Fri, 02 May 2014 14:29:29 -0700 (PDT) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:from:to:subject:in-reply-to:references + :user-agent:date:message-id:mime-version:content-type; + bh=TaVV0J3I0s0nlIKYz9XlM9kH56SFcPV/Q8eYZBARKP0=; + b=l/jN6t0P+hZezw8jngyv6uqaPSspSe/D2rVG1M7fS6tlfd7DAr3rpBrQ7sCXOAKxcc + M20MOVa+TuuAr+FtdpQWZdNetasAXxzUk6OPOS+0k7vwd9/M7ro1EIeH0tHg+ltLUdxU + 7B2aokdzi075fOZu/TMkrUhLA1RF5q1lRmLON+aMAfuhODDvwCVOLjkgjFyMBaDDu2dO + Zo7JvG5wpxeUKqmI1MT6ZcpfiGl7Ajc+xTlq/qsVjFdUblnaVotzkafp1DTa5COg4B// + J0Ky6elDyCdkkGtipykxMFdXk4FkCb1LU2iI6kxGVuQoqPGkUURoUNcOTlqEeLmY6UoA + YYKQ== +X-Gm-Message-State: + ALoCoQnwQ8QvDdlLHFTSLnthsRI0+majfV6kdWnSKSwnga6rn6lEypnCVEOBRzcY+4VysBZU847t +X-Received: by 10.14.241.137 with SMTP id g9mr3437207eer.69.1399066169272; + Fri, 02 May 2014 14:29:29 -0700 (PDT) +Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi. + [88.195.111.91]) + by mx.google.com with ESMTPSA id y51sm7577387eeu.0.2014.05.02.14.29.27 + for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Fri, 02 May 2014 14:29:28 -0700 (PDT) +From: Jani Nikula +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.18~rc0+2~gbc64cdc (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-pc-linux-gnu) +Date: Sat, 03 May 2014 00:29:27 +0300 +Message-ID: <87zjizyimg.fsf@nikula.org> +MIME-Version: 1.0 +Content-Type: text/plain +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 21:29:38 -0000 + +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: + +First, read Mark's reply about database upgrade, and heed the notice +about upgrade being automatic but downgrade requiring a reindex of all +your mails. + +Here's additional commentary on the specific queries. + +> linux7$ ./notmuch count folder:mail +> 0 +> linux8$ ./notmuch count folder:.mail +> 0 + +These two will not match anything. + +> linux9$ ./notmuch count folder:.mail.voicemail +> 0 + +After the upgrade, this should work for .mail.voicemail/{new,cur}. + +> linux10$ ./notmuch count folder:.mail.voicemail/cur +> 0 + +This won't match anything. To specifically search for messages in cur, +you can use the new path prefix, path:.mail.voicemail/cur + +> linux 11$ ./notmuch count path:.mail.voicemail +> 0 + +This will match messages in .mail.voicemail only, and nothing in the cur +or new subdirectories. + +> linux 12$ ./notmuch count path:.mail.voicemail/'**' +> 0 + +I'm not sure your quoting will work, but if you don't have any other +subfolders than cur and new, this should be equal to +folder:.mail.voicemail + +> linux 13$ ./notmuch count path:.mail.voicemail/cur +> 0 + +This should match messages in the cur subdirectory. + +> linux 14$ ./notmuch count folder:mail.voicemail +> 0 + +This won't match anything. + + +BR, +Jani. + -- 2.26.2