Re: notmuch.el: controlling what does and doesn't get expanded in searches
[notmuch-archives.git] / db / fd7606ee2dfdb9f027ea2c127f899d40ba110f
1 Return-Path: <aidecoe@aidecoe.name>\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 arlo.cworth.org (Postfix) with ESMTP id 5997B6DE1329\r
6  for <notmuch@notmuchmail.org>; Tue,  1 Sep 2015 15:52:52 -0700 (PDT)\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -0.004\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[AWL=0.097,\r
12   DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001]\r
13  autolearn=disabled\r
14 Received: from arlo.cworth.org ([127.0.0.1])\r
15  by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
16  with ESMTP id VOyg3aCieq3h for <notmuch@notmuchmail.org>;\r
17  Tue,  1 Sep 2015 15:52:50 -0700 (PDT)\r
18 Received: from jim.zolnowski.name (jim.zolnowski.name [188.116.54.122])\r
19  by arlo.cworth.org (Postfix) with ESMTPS id 0AA826DE1226\r
20  for <notmuch@notmuchmail.org>; Tue,  1 Sep 2015 15:52:49 -0700 (PDT)\r
21 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;\r
22  d=aidecoe.name; s=jim;\r
23   h=Content-Type:MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From; bh=vhgQQnGbpXfcbjn5ua5AJV+d7HbrVgbjYasxGwyQFP4=;\r
24   b=knczbbPimt3+1oxoW0ql1igRU9pmckNniIqD4E3nEuZozafqEU9erjj5gekmEl4ms1NJFALOzjsPB1AU+6IQEGB3nXsZDmaFlG9mMP+xLL2YFe56qJYYZqDlD0fXnrcuUtg0OYbi0O4Pjk/laFjZVm8EanNW/wo/GNBJeS44EuLV/cytvQD85mA0PMQZFg4t83/gYwyjRIayeIQcHQb/VlD0uVT8DwamsH73grd0MX85ApQQQ3U15M+hRVuvEagBIu8dG7j8U0W7HLHjtwwVhzopP4wsCAZcSNIi/GhttxBrpdGZ2KQ3zcEHwRI/6M8gmTL4ELh4XKekYydMaOzoqA==;\r
25 Received: from cpc3-cmbg17-2-0-cust294.5-4.cable.virginm.net ([86.22.65.39]\r
26  helo=localhost)\r
27  by jim.zolnowski.name with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256)\r
28  (Exim 4.85) (envelope-from <aidecoe@aidecoe.name>)\r
29  id 1ZWuPy-0006K1-RC; Wed, 02 Sep 2015 00:52:43 +0200\r
30 From: Amadeusz =?utf-8?B?xbtvxYJub3dza2k=?= <aidecoe@aidecoe.name>\r
31 To: David Mazieres expires 2015-11-29 PST\r
32  <mazieres-sggp47c7j46624db3rharctcei@temporary-address.scs.stanford.edu>\r
33 Subject: Re: muchsync files renames\r
34 In-Reply-To: <878u8rvxap.fsf@ta.scs.stanford.edu>\r
35 References: <878u93ujdo.fsf@freja.aidecoe.name>\r
36  <876146o920.fsf@ta.scs.stanford.edu> <871teu8kdd.fsf@freja.aidecoe.name>\r
37  <87oahxojlv.fsf@ta.scs.stanford.edu> <87vbbwnbb4.fsf@freja.aidecoe.name>\r
38  <87io7wr50y.fsf@ta.scs.stanford.edu> <87k2sbmzww.fsf@freja.aidecoe.name>\r
39  <87oahnmkqf.fsf@ta.scs.stanford.edu> <87egijm7kw.fsf@freja.aidecoe.name>\r
40  <878u8rvxap.fsf@ta.scs.stanford.edu>\r
41 User-Agent: Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.5.1\r
42  (x86_64-pc-linux-gnu)\r
43 Date: Tue, 01 Sep 2015 23:52:37 +0100\r
44 Message-ID: <87613tn45m.fsf@freja.aidecoe.name>\r
45 MIME-Version: 1.0\r
46 Content-Type: multipart/signed; boundary="=-=-=";\r
47  micalg=pgp-sha512; protocol="application/pgp-signature"\r
48 Cc: notmuch@notmuchmail.org\r
49 X-BeenThere: notmuch@notmuchmail.org\r
50 X-Mailman-Version: 2.1.18\r
51 Precedence: list\r
52 List-Id: "Use and development of the notmuch mail system."\r
53  <notmuch.notmuchmail.org>\r
54 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
55  <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
56 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
57 List-Post: <mailto:notmuch@notmuchmail.org>\r
58 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
59 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
60  <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
61 X-List-Received-Date: Tue, 01 Sep 2015 22:52:52 -0000\r
62 \r
63 --=-=-=\r
64 Content-Type: text/plain; charset=utf-8\r
65 Content-Transfer-Encoding: quoted-printable\r
66 \r
67 Hi David,\r
68 \r
69 David Mazieres <dm-list-email-notmuch@scs.stanford.edu> writes:\r
70 > Let's just make sure I understand:  Your mail starts out like this:\r
71 >\r
72 >     Path:  spam/new/nnn.MnnnPnnnQnRn.machine\r
73 >     Tags:  new\r
74 >\r
75 > Then you run afew, and afew runs\r
76 >\r
77 >     notmuch tag -new +spam <message-ID>\r
78 >\r
79 > You are saying that that even though maildir.synchronize_tags is true,\r
80 > you end up with:\r
81 >\r
82 >     Path:  spam/new/nnn.MnnnPnnnQnRn.machine\r
83 >     Tags:  spam\r
84 \r
85 Yes.\r
86 \r
87 \r
88 > That's a little surprising, because the next time you run "notmuch new,"\r
89 > I would have expected it to add the unread flag based on the pathname.\r
90 \r
91 What's more surprising is that there is a test case in notmuch test\r
92 suite which test whether after modifing tag of a mail it is moved from\r
93 new/ to cur/. Yes, it should be moved on any tag modification if I\r
94 understand correctly. But it seems it does not for my maildirs...\r
95 \r
96 $ notmuch search --output=3Dfiles thread:00000000000108bf\r
97 /home/aidecoe/Mail/aidecoe/2015/new/1441022521.M714465P23412V000000000000FE=\r
98 04I0000000000141A38_0.freja,S=3D53857\r
99 $ notmuch search thread:00000000000108bf\r
100 thread:00000000000108bf  Yest. 11:58 [1/1] Somebody; Subject (reklama unrea=\r
101 d)\r
102 $ notmuch tag +hey thread:00000000000108bf\r
103 $ notmuch search thread:00000000000108bf\r
104 thread:00000000000108bf  Yest. 11:58 [1/1] Somebody; Subject (hey reklama u=\r
105 nread)\r
106 $ notmuch search --output=3Dfiles thread:00000000000108bf\r
107 /home/aidecoe/Mail/aidecoe/2015/new/1441022521.M714465P23412V000000000000FE=\r
108 04I0000000000141A38_0.freja,S=3D53857\r
109 \r
110 \r
111 > Then it will add the unread tag to the Xapian database.  But maybe if it\r
112 > finds a file in the new folder it doesn't add the unread flag.\r
113 \r
114 Might be.\r
115 \r
116 \r
117 > But why does notmuch_message_tags_to_maildir_flag() then feel the need\r
118 > to rename the file when muchsync calls it.  Muchsync should ideally\r
119 > behave exactly the same as the notmuch tag command.  Specifically, when\r
120 > muchsync receives a new file from the server, it does the following:\r
121 >\r
122 >  1. create file in same directory as the server (presumably spam/new)\r
123 >\r
124 >  2. Call the following functions on this file:\r
125 >       notmuch_database_add_message()\r
126 >       notmuch_message_freeze()\r
127 >       notmuch_message_remove_all_tags()\r
128 >       notmuch_message_add_tag() for each tag in new.tags\r
129 >       if (synchronize_tags) notmuch_message_tags_to_maildir_flag()\r
130 >       notmuch_message_thaw()\r
131 >\r
132 >  3. get the current tags of the message from the server (presumably just\r
133 >     spam)\r
134 >\r
135 >  4. Call the following functions on the Message-ID:\r
136 >       notmuch_message_freeze()\r
137 >       notmuch_message_remove_all_tags()\r
138 >       notmuch_message_add_tag() for each tag sent *by the server*\r
139 >       if (synchronize_tags) notmuch_message_tags_to_maildir_flag()\r
140 >       notmuch_message_thaw()\r
141 \r
142 So for some reason in my maildirs mails are not moved from new/ to cur/\r
143 on tag manipulation, but they are on client side by muchsync.  I will\r
144 have to investigate why this happens to me.\r
145 \r
146 \r
147 =2D-=20\r
148 Amadeusz =C5=BBo=C5=82nowski\r
149 \r
150 --=-=-=\r
151 Content-Type: application/pgp-signature; name="signature.asc"\r
152 \r
153 -----BEGIN PGP SIGNATURE-----\r
154 Version: GnuPG v2.1\r
155 \r
156 iQJ8BAEBCgBmBQJV5iw1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
157 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCMzcyRTFENjI5NUM1MzYwQTQwODQyRUZD\r
158 QkNDODAyM0Y1OUUxNzA0AAoJEMvMgCP1nhcExfUP/2oRePjDcI+XXfvxzvN6Knbv\r
159 JZgUF20evMpb5UhUW+4EJFpjE6GBiyY+RopbGduTHbf1eGGCNd6e4P2NlAVyZMcO\r
160 YZeluU+upeH47w5qYacRKOTcq6+UIvsHsArLSgYCR1eV9RIMcZ/7sj83KDc8CNY8\r
161 uIunRoCn9Xpfm9QsnbfxzY3Vr4TqsvHaHc21MbjLk7ccNvTBYJqxtT+xZIZ5oxf4\r
162 bKzIxiPQnZYUTE60y9mk+PWHEMBIJZVLoMYPaK4v16LZf6jPP1i+WUvAHZLBYH04\r
163 lbEeQ42FMMBM71cWIz1kGwq0MQEEhMcsAq/Vlo8dIko873gkO5X3kgnaLleKzx66\r
164 VyQB9DwF2sewht844u0rYaJfCpLpy6Lz3JH0g/wcWD41LiakycFOudIGFem4tO7i\r
165 pvfpCXS4nXFOqoRF+anT3aegM2KTcDzDDYRuJ3bXinxevfwUWb1583RkRvPSJw/p\r
166 +lWJxuFb9wSQLtR+JBHAs6yfyoYywc5F4xeJck3Xryyp0HOU6sBTjcO5L5iQjUQB\r
167 HWkCX+y/q4wtaL/u5+RxUsDprUD5GlKAnhpXVaNJ3wWZjqyn18Gp8n0QkeAROjfU\r
168 qy51gKONHzwtiVDoa9cduArdLocHH5cMNOceKqh+HeB5+LG84JkRV/46p9tZ96PB\r
169 LawSmgryk//VneCkeky4\r
170 =tHzz\r
171 -----END PGP SIGNATURE-----\r
172 --=-=-=--\r