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