1 Return-Path: <cworth@cworth.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id C213140DBF5
\r
6 for <notmuch@notmuchmail.org>; Thu, 11 Nov 2010 10:20:25 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5
\r
12 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01]
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id eDU1QXq8IYUX; Thu, 11 Nov 2010 10:20:14 -0800 (PST)
\r
17 Received: from yoom.home.cworth.org (localhost [127.0.0.1])
\r
18 by olra.theworths.org (Postfix) with ESMTP id C5ADF40DBD3;
\r
19 Thu, 11 Nov 2010 10:20:14 -0800 (PST)
\r
20 Received: by yoom.home.cworth.org (Postfix, from userid 1000)
\r
21 id 4DC4F25412B; Thu, 11 Nov 2010 10:20:14 -0800 (PST)
\r
22 From: Carl Worth <cworth@cworth.org>
\r
23 To: Michal Sojka <sojkam1@fel.cvut.cz>, notmuch@notmuchmail.org
\r
24 Subject: Re: [PATCH v4 0/4] Maildir synchronization
\r
25 In-Reply-To: <87vd43hn9b.fsf@steelpick.2x.cz>
\r
26 References: <87tyk3vpxd.fsf@wsheee.2x.cz>
\r
27 <1288560558-18915-1-git-send-email-sojkam1@fel.cvut.cz>
\r
28 <877hgsrjau.fsf@yoom.home.cworth.org> <87d3qhq527.fsf@resox.2x.cz>
\r
29 <874obrmww9.fsf@yoom.home.cworth.org>
\r
30 <87iq066cbd.fsf@steelpick.2x.cz>
\r
31 <87oc9ykzae.fsf@yoom.home.cworth.org>
\r
32 <877hgm2hjg.fsf@steelpick.2x.cz>
\r
33 <87lj52knbp.fsf@yoom.home.cworth.org>
\r
34 <874obp325b.fsf@steelpick.2x.cz>
\r
35 <87fwv9ktu1.fsf@yoom.home.cworth.org>
\r
36 <87mxpgq50f.fsf@yoom.home.cworth.org>
\r
37 <87vd43hn9b.fsf@steelpick.2x.cz>
\r
38 User-Agent: Notmuch/0.4 (http://notmuchmail.org) Emacs/23.2.1
\r
40 Date: Thu, 11 Nov 2010 10:20:03 -0800
\r
41 Message-ID: <87d3qboh7w.fsf@yoom.home.cworth.org>
\r
43 Content-Type: multipart/signed; boundary="=-=-=";
\r
44 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
45 X-BeenThere: notmuch@notmuchmail.org
\r
46 X-Mailman-Version: 2.1.13
\r
48 List-Id: "Use and development of the notmuch mail system."
\r
49 <notmuch.notmuchmail.org>
\r
50 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
52 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
53 List-Post: <mailto:notmuch@notmuchmail.org>
\r
54 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
55 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
56 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
57 X-List-Received-Date: Thu, 11 Nov 2010 18:20:25 -0000
\r
60 Content-Transfer-Encoding: quoted-printable
\r
62 On Thu, 11 Nov 2010 16:51:28 +0100, Michal Sojka <sojkam1@fel.cvut.cz> wrot=
\r
64 > Does this mean, that if I want to remove the replied tag (for example) I
\r
65 > can still do it by manipulating flags, i.e. I would remove the R flag
\r
66 > from all messages with the coreposnding Message-ID? Or does it mean that
\r
67 > the only way is to remove the replied tag in notmuch? I'd prefer the
\r
70 It is the former, yes. See, for example the following test in the test
\r
73 "Removing 'S' flag from existing filename adds 'unread' tag"
\r
75 Also, here is the latest documentation of
\r
76 notmuch_message_maildir_flags_to_tags. If this could be made more clear,
\r
79 /* Add/remove tags according to maildir flags in the message filename(s)
\r
81 * This function examines the filenames of 'message' for maildir
\r
82 * flags, and adds or removes tags on 'message' as follows when these
\r
83 * flags are present:
\r
85 * Flag Action if present
\r
86 * ---- -----------------
\r
87 * 'D' Adds the "draft" tag to the message
\r
88 * 'F' Adds the "flagged" tag to the message
\r
89 * 'P' Adds the "passed" tag to the message
\r
90 * 'R' Adds the "replied" tag to the message
\r
91 * 'S' Removes the "unread" tag from the message
\r
93 * For each flag that is not present, the opposite action (add/remove)
\r
94 * is performed for the corresponding tags.
\r
96 * Flags are identified as trailing components of the filename after a
\r
97 * sequence of ":2,".
\r
99 * If there are multiple filenames associated with this message, the
\r
100 * flag is considered present if it appears in one or more
\r
101 * filenames. (That is, the flags from the multiple filenames are
\r
102 * combined with the logical OR operator.)
\r
104 * A client can ensure that notmuch database tags remain synchronized
\r
105 * with maildir flags by calling this function after each call to
\r
106 * notmuch_database_add_message. See also
\r
107 * notmuch_message_tags_to_maildir_flags for synchronizing tag changes
\r
108 * back to maildir flags.
\r
114 carl.d.worth@intel.com
\r
117 Content-Type: application/pgp-signature
\r
119 -----BEGIN PGP SIGNATURE-----
\r
120 Version: GnuPG v1.4.10 (GNU/Linux)
\r
122 iD8DBQFM3DPT6JDdNq8qSWgRAja8AKCZc5zigd7uGZqP9Imsn+Y39bE0GwCgpDz3
\r
123 Z4QRO0NhCiDWBh/QklbKURg=
\r
125 -----END PGP SIGNATURE-----
\r