Re: synchronizing tag for cur/new location of mail

diff --git a/2d/39f471876883dfab9f60cb6e53ae74e39dcd9e b/2d/39f471876883dfab9f60cb6e53ae74e39dcd9e
new file mode 100644 (file)
index 0000000..0b6f19b
--- /dev/null
+++ b/2d/39f471876883dfab9f60cb6e53ae74e39dcd9e
@@ -0,0 +1,101 @@
+Return-Path: <jani@nikula.org>\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 EAEF5431FAE\r
+       for <notmuch@notmuchmail.org>; Tue, 12 Mar 2013 03:24:58 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[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 VxOKg8hspNjs for <notmuch@notmuchmail.org>;\r
+       Tue, 12 Mar 2013 03:24:58 -0700 (PDT)\r
+Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com\r
+ [74.125.82.47])       (using TLSv1 with cipher RC4-SHA (128/128 bits))        (No client\r
+ certificate requested)        by olra.theworths.org (Postfix) with ESMTPS id\r
+ 22DD0431FAF   for <notmuch@notmuchmail.org>; Tue, 12 Mar 2013 03:24:57 -0700\r
+ (PDT)\r
+Received: by mail-wg0-f47.google.com with SMTP id dr13so6043782wgb.14\r
+       for <notmuch@notmuchmail.org>; Tue, 12 Mar 2013 03:24:56 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=google.com; s=20120113;\r
+       h=x-received:from:to:subject:in-reply-to:references:user-agent:date\r
+       :message-id:mime-version:content-type:x-gm-message-state;\r
+       bh=qeua8fVjIU6vGhfmfOuVoJ/MbZp5LTvlL4hY6zq4DFc=;\r
+       b=pmn3yl7/CeNfV6MT8neUwYfTFkZTzGj4upmsnfNHfF9dn24Y6MnPVwgodn3qDLj1jo\r
+       F4WqV0fCn/TnEbknhC47f+kE9lSZThWl0FqF5mop37Jxx/RiXQ9iE3kcQFOAwA+ZI8b4\r
+       KJ+2yWNGqBGllAkeI6zxT+wr5+1j1UfV9iXJclHjzgJTVR4j7I2FC5XeKQ+ZXHzXklu2\r
+       0gJBoIEENuiakowXK15ZTHT/4GcNvpzavMnPUTMJWadeOmRQOI6reN9v17AT/szCBaNQ\r
+       NmTEDAtwaR5QORj8camfFrUcPH9jF3lg6WNgEH4kZcuVxhrEorCHDXgR9RifkL5ss/c3\r
+       bZ8g==\r
+X-Received: by 10.194.62.170 with SMTP id z10mr25282289wjr.34.1363083895520;\r
+       Tue, 12 Mar 2013 03:24:55 -0700 (PDT)\r
+Received: from localhost ([2001:4b98:dc0:43:216:3eff:fe1b:25f3])\r
+       by mx.google.com with ESMTPS id q13sm26317149wie.0.2013.03.12.03.24.53\r
+       (version=TLSv1.1 cipher=RC4-SHA bits=128/128);\r
+       Tue, 12 Mar 2013 03:24:54 -0700 (PDT)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Daniel <quite@hack.org>, notmuch@notmuchmail.org\r
+Subject: Re: synchronizing tag for cur/new location of mail\r
+In-Reply-To: <khmt34$7k2$1@ger.gmane.org>\r
+References: <khmt34$7k2$1@ger.gmane.org>\r
+User-Agent: Notmuch/0.15.2+34~ga90fdd9 (http://notmuchmail.org) Emacs/23.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Tue, 12 Mar 2013 11:24:44 +0100\r
+Message-ID: <871ubkdifn.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Gm-Message-State:\r
+ ALoCoQm3stsh9a5U2nVqoAAamWA6FbqjWKaKwRoyZsvKkI9tSjJvGTQGry9xhwKLswwQqF7oZRC3\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: Tue, 12 Mar 2013 10:24:59 -0000\r
+\r
+On Tue, 12 Mar 2013, Daniel <quite@hack.org> wrote:\r
+> Is there currently no automatic tag that reflects whether a mail was\r
+> found in folder/cur or folder/new? The "unread" tag properly reflects\r
+> the maildir ",S" flag, but the one named "new" doesn't seem to be\r
+> automatic in any way, right?\r
+\r
+That's correct, there's no such automatic tag.\r
+\r
+The "new" tag is in no way special to notmuch. It's just a typically\r
+used temp tag, usually added by 'notmuch new' based on the user's\r
+new.tags config, and removed by the user's post-new hook.\r
+\r
+> I mostly use notmuch as a search backend to mutt, and it certainly is\r
+> very useful. Though since I started feeding rss to maildir, I would like\r
+> the idea of presenting somewhere in my system a list of new and "unseen"\r
+> mails (in the mutt sense, kind of, which you might be familiar with).\r
+\r
+>From notmuch perspective the difference between "new" and "cur" is just\r
+that the message files in "new" have no maildir flags set, and once\r
+maildir flags are set, they are moved to "cur". No additional semantics\r
+is applied to the file location.\r
+\r
+> Presently this seems impossible.\r
+\r
+A search for folder:new might be helpful, depending on your setup.\r
+\r
+It seems that you may get surprising results if you have more than one\r
+file with the same message-id, and some of those files are in "new" and\r
+some in "cur". (Any code to support automatic "new" tag would have to\r
+handle this too.)\r
+\r
+\r
+HTH,\r
+Jani.\r