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 C213140DBF5 for ; Thu, 11 Nov 2010 10:20:25 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.89 X-Spam-Level: X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01] autolearn=ham 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 eDU1QXq8IYUX; Thu, 11 Nov 2010 10:20:14 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id C5ADF40DBD3; Thu, 11 Nov 2010 10:20:14 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id 4DC4F25412B; Thu, 11 Nov 2010 10:20:14 -0800 (PST) From: Carl Worth To: Michal Sojka , notmuch@notmuchmail.org Subject: Re: [PATCH v4 0/4] Maildir synchronization In-Reply-To: <87vd43hn9b.fsf@steelpick.2x.cz> References: <87tyk3vpxd.fsf@wsheee.2x.cz> <1288560558-18915-1-git-send-email-sojkam1@fel.cvut.cz> <877hgsrjau.fsf@yoom.home.cworth.org> <87d3qhq527.fsf@resox.2x.cz> <874obrmww9.fsf@yoom.home.cworth.org> <87iq066cbd.fsf@steelpick.2x.cz> <87oc9ykzae.fsf@yoom.home.cworth.org> <877hgm2hjg.fsf@steelpick.2x.cz> <87lj52knbp.fsf@yoom.home.cworth.org> <874obp325b.fsf@steelpick.2x.cz> <87fwv9ktu1.fsf@yoom.home.cworth.org> <87mxpgq50f.fsf@yoom.home.cworth.org> <87vd43hn9b.fsf@steelpick.2x.cz> User-Agent: Notmuch/0.4 (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Thu, 11 Nov 2010 10:20:03 -0800 Message-ID: <87d3qboh7w.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" 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: Thu, 11 Nov 2010 18:20:25 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Thu, 11 Nov 2010 16:51:28 +0100, Michal Sojka wrot= e: > Does this mean, that if I want to remove the replied tag (for example) I > can still do it by manipulating flags, i.e. I would remove the R flag > from all messages with the coreposnding Message-ID? Or does it mean that > the only way is to remove the replied tag in notmuch? I'd prefer the > first. It is the former, yes. See, for example the following test in the test suite: "Removing 'S' flag from existing filename adds 'unread' tag" Also, here is the latest documentation of notmuch_message_maildir_flags_to_tags. If this could be made more clear, please let me know: /* Add/remove tags according to maildir flags in the message filename(s) * * This function examines the filenames of 'message' for maildir * flags, and adds or removes tags on 'message' as follows when these * flags are present: * * Flag Action if present * ---- ----------------- * 'D' Adds the "draft" tag to the message * 'F' Adds the "flagged" tag to the message * 'P' Adds the "passed" tag to the message * 'R' Adds the "replied" tag to the message * 'S' Removes the "unread" tag from the message * * For each flag that is not present, the opposite action (add/remove) * is performed for the corresponding tags. * * Flags are identified as trailing components of the filename after a * sequence of ":2,". * * If there are multiple filenames associated with this message, the * flag is considered present if it appears in one or more * filenames. (That is, the flags from the multiple filenames are * combined with the logical OR operator.) * * A client can ensure that notmuch database tags remain synchronized * with maildir flags by calling this function after each call to * notmuch_database_add_message. See also * notmuch_message_tags_to_maildir_flags for synchronizing tag changes * back to maildir flags. */ =2DCarl =2D-=20 carl.d.worth@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFM3DPT6JDdNq8qSWgRAja8AKCZc5zigd7uGZqP9Imsn+Y39bE0GwCgpDz3 Z4QRO0NhCiDWBh/QklbKURg= =tQP5 -----END PGP SIGNATURE----- --=-=-=--