Re: muchsync files renames

diff --git a/8e/fcfc1918f83e1f5e5ffd24df527023d1ff0934 b/8e/fcfc1918f83e1f5e5ffd24df527023d1ff0934
new file mode 100644 (file)
index 0000000..d79ff9c
--- /dev/null
+++ b/8e/fcfc1918f83e1f5e5ffd24df527023d1ff0934
@@ -0,0 +1,97 @@
+Return-Path:\r
+ <return-xy9svedfjhgjf6qfbji4fcu42w@temporary-address.scs.stanford.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id D968B6DE17FB\r
+ for <notmuch@notmuchmail.org>; Tue,  1 Sep 2015 17:46:32 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.944\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.944 tagged_above=-999 required=5 tests=[AWL=0.163,\r
+  RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001,\r
+  URIBL_SBL=0.644, URIBL_SBL_A=0.1] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id GLal4zgAVkSx for <notmuch@notmuchmail.org>;\r
+ Tue,  1 Sep 2015 17:46:31 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 10B3A6DE175C\r
+ for <notmuch@notmuchmail.org>; Tue,  1 Sep 2015 17:46:31 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (localhost.scs.stanford.edu\r
+ [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id\r
+ t820kOEl024718; Tue, 1 Sep 2015 17:46:24 -0700 (PDT)\r
+Received: (from dm@localhost)\r
+ by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id t820kOJf013638;\r
+ Tue, 1 Sep 2015 17:46:24 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+ return-xy9svedfjhgjf6qfbji4fcu42w@ta.scs.stanford.edu using -f\r
+From: dm-list-email-notmuch@scs.stanford.edu\r
+To: David Bremner <david@tethera.net>, Amadeusz =?utf-8?B?xbtvxYJub3dza2k=?=\r
+ <aidecoe@aidecoe.name>\r
+Subject: Re: muchsync files renames\r
+In-Reply-To: <87vbbthd1m.fsf@maritornes.cs.unb.ca>\r
+References: <878u93ujdo.fsf@freja.aidecoe.name>\r
+ <876146o920.fsf@ta.scs.stanford.edu> <871teu8kdd.fsf@freja.aidecoe.name>\r
+ <87oahxojlv.fsf@ta.scs.stanford.edu> <87vbbwnbb4.fsf@freja.aidecoe.name>\r
+ <87io7wr50y.fsf@ta.scs.stanford.edu> <87k2sbmzww.fsf@freja.aidecoe.name>\r
+ <87oahnmkqf.fsf@ta.scs.stanford.edu> <87egijm7kw.fsf@freja.aidecoe.name>\r
+ <878u8rvxap.fsf@ta.scs.stanford.edu> <87613tn45m.fsf@freja.aidecoe.name>\r
+ <87vbbthd1m.fsf@maritornes.cs.unb.ca>\r
+Date: Tue, 01 Sep 2015 17:46:24 -0700\r
+Message-ID: <874mjd3axr.fsf@ta.scs.stanford.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.18\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: Wed, 02 Sep 2015 00:46:33 -0000\r
+\r
+David Bremner <david@tethera.net> writes:\r
+\r
+> Amadeusz =C5=BBo=C5=82nowski <aidecoe@aidecoe.name> writes:\r
+>\r
+>> What's more surprising is that there is a test case in notmuch test\r
+>> suite which test whether after modifing tag of a mail it is moved from\r
+>> new/ to cur/. Yes, it should be moved on any tag modification if I\r
+>> understand correctly. But it seems it does not for my maildirs...\r
+>>\r
+>\r
+> If I understand the code correctly, this movement will only happen when\r
+> one of the maildir-flag-equivalent tags is changed. I haven't dug ack\r
+> through the archives, but I think mutt uses presence in new/ as some\r
+> kind of extra unseen state, so people requested not to move files until\r
+> needed.\r
+\r
+Can you explain how/where this is implemented?  I would like muchsync to\r
+do exactly what notmuch does, and ideally without replicating its logic,\r
+if I can just have libnotmuch handle this.  Currently, my code looks\r
+something like this:\r
+\r
+      notmuch_message_freeze()\r
+      notmuch_message_remove_all_tags()\r
+      notmuch_message_add_tag(); notmuch_message_add_tag(); ...\r
+      if (synchronize_tags)\r
+        notmuch_message_tags_to_maildir_flag()\r
+      notmuch_message_thaw()\r
+\r
+And what we're finding is the above code causes the message to move from\r
+new/ to cur/, while the "notmuch tag" command does not, even while\r
+changing between the same before and after tag sets.\r
+\r
+Any ideas?\r
+\r
+Thanks,\r
+David\r