2 <return-m5bnw98qfab3x8rrwucsc97r9e@temporary-address.scs.stanford.edu>
\r
3 X-Original-To: notmuch@notmuchmail.org
\r
4 Delivered-To: notmuch@notmuchmail.org
\r
5 Received: from localhost (localhost [127.0.0.1])
\r
6 by arlo.cworth.org (Postfix) with ESMTP id E3ECE6DE0B26
\r
7 for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 12:41:14 -0700 (PDT)
\r
8 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
9 X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "References"
\r
11 X-Spam-Score: -1.798
\r
13 X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[AWL=0.309,
\r
14 RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001,
\r
15 URIBL_SBL=0.644, URIBL_SBL_A=0.1] autolearn=disabled
\r
16 Received: from arlo.cworth.org ([127.0.0.1])
\r
17 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
18 with ESMTP id Hva2JRWxVmst for <notmuch@notmuchmail.org>;
\r
19 Sun, 16 Aug 2015 12:41:13 -0700 (PDT)
\r
20 Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])
\r
21 by arlo.cworth.org (Postfix) with ESMTPS id 2713A6DE01D3
\r
22 for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 12:41:13 -0700 (PDT)
\r
23 Received: from market.scs.stanford.edu (localhost.scs.stanford.edu
\r
24 [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id
\r
25 t7GJfCSm001264 for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 12:41:12 -0700
\r
27 Received: (from dm@localhost)
\r
28 by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id t7GJfCXX012637;
\r
29 Sun, 16 Aug 2015 12:41:12 -0700 (PDT)
\r
30 X-Authentication-Warning: market.scs.stanford.edu: dm set sender to
\r
31 return-m5bnw98qfab3x8rrwucsc97r9e@ta.scs.stanford.edu using -f
\r
32 From: dm-list-email-notmuch@scs.stanford.edu
\r
33 To: notmuch@notmuchmail.org
\r
34 Subject: Re: Enabling and disabling maildir.synchronize_flags
\r
35 In-Reply-To: <87614ffl0t.fsf@maritornes.cs.unb.ca>
\r
36 Date: Sun, 16 Aug 2015 12:34:30 -0700
\r
37 References: <87r3orbqfn.fsf@ta.scs.stanford.edu>
\r
38 <87r3n3fu7d.fsf@maritornes.cs.unb.ca> <874mjzblwc.fsf@ta.scs.stanford.edu>
\r
39 <87614ffl0t.fsf@maritornes.cs.unb.ca> <87vbcf9ge1.fsf@ta.scs.stanford.edu>
\r
40 References: <87r3orbqfn.fsf@ta.scs.stanford.edu>
\r
41 <87r3n3fu7d.fsf@maritornes.cs.unb.ca> <874mjzblwc.fsf@ta.scs.stanford.edu>
\r
42 <87614ffl0t.fsf@maritornes.cs.unb.ca>
\r
43 Message-ID: <87pp2n9g2v.fsf@ta.scs.stanford.edu>
\r
45 Content-Type: text/plain
\r
46 X-BeenThere: notmuch@notmuchmail.org
\r
47 X-Mailman-Version: 2.1.18
\r
49 List-Id: "Use and development of the notmuch mail system."
\r
50 <notmuch.notmuchmail.org>
\r
51 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
52 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
53 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
54 List-Post: <mailto:notmuch@notmuchmail.org>
\r
55 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
56 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
57 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
58 X-List-Received-Date: Sun, 16 Aug 2015 19:41:15 -0000
\r
60 David Bremner <david@tethera.net> writes:
\r
62 > David Mazieres <dm-list-email-notmuch@scs.stanford.edu> writes:
\r
63 >> So my question remains, what's the easiest safe way to re-enable
\r
64 [ 2 more citation lines. Click/Enter to show. ]
\r
65 >> synchronize_flags after disabling it? (Safe meaning it won't change any
\r
66 >> tags.) It could be that there's a very simple answer, in which case
\r
67 >> sticking it in the man page might be nice.
\r
69 > I can't think of a simple, safe, and fast answer.
\r
71 Okay, thanks. At least I wasn't missing something obvious.
\r
73 > 2) when the lastmod changes go in, it seems like you could run the first
\r
74 > notmuch new after enabling tag synchonizing, and dump only the tag
\r
75 > changes since a checkpoint lastmod value. This would allow rolling
\r
76 > back the unwanted tag changes.
\r
78 Indeed, one of many reasons I'm eagerly awaiting lastmod changes.
\r
80 > [1]: see this potential test, if for some reason we wanted to
\r
81 > guarantee this behaviours.
\r
83 If we did want this, I'm assuming it would take the form of a new option
\r
84 to notmuch new (--override-flags) which says to do the synchronization
\r
85 in the other direction (Xapian -> Maildir)? There would be benefit to
\r
86 having such a flag, but I don't know how hard it would be to implement,
\r
87 so I can't do the cost/benefit analysis.
\r
89 As a kind of aside, one reason people might want to synchronize flags is
\r
90 for mobile device support. I don't regularly access my email from my
\r
91 mobile phone, but on those rare occasions when I might need to, I set up
\r
92 an IMAP server and use an imap client on the phone. I wonder if anyone
\r
93 has thought about implementing an IMAP-ish server directly on top of
\r
94 libnotmuch. (I say IMAP-ish because the obvious SEARCH command
\r
95 implementation wouldn't be RFC3501-compliant, but who cares when notmuch
\r
96 has something better.)
\r
98 Does anyone else use both notmuch but also access email from a mobile
\r
99 device? If so what do you do?
\r