From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Enabling and disabling maildir.synchronize_flags
Date: Sun, 16 Aug 2015 02:52:35 -0700 [thread overview]
Message-ID: <874mjzblwc.fsf@ta.scs.stanford.edu> (raw)
In-Reply-To: <87r3n3fu7d.fsf@maritornes.cs.unb.ca>
David Bremner <david@tethera.net> writes:
> dm-list-email-notmuch@scs.stanford.edu writes:
>
>> It seems that disabling it should simply be safe. But re-enabling, one
>> risks losing tags, as the next notmuch new will cause old maildir flags
>> to override the xapian database. So that suggests something like:
>>
>> notmuch dump > backup
>> notmuch config set maildir.synchronize_flags false
>> # Do I need to run notmuch new here?
>> notmuch restore < backup
>
> Hi David;
>
> Sorry about the long delay. I'm not sure I follow the connection between
> your paragraph above and the the example. The example seems safe, but as
> you say, disabling synching should bs safe anyway.
It's not an example, it's kind of a worst case scenario if there's no
easy and safe way way to enable synchronize_flags. I want to try
disabling flags, but if I change my mind and the only way to get it back
is to do a full notmuch dump/restore, that's a pretty hefty penalty.
Also, even if I do a full notmuch dump / restore, I'm not sure if the
notmuch new is necessary in the middle.
So my question remains, what's the easiest safe way to re-enable
synchronize_flags after disabling it? (Safe meaning it won't change any
tags.) It could be that there's a very simple answer, in which case
sticking it in the man page might be nice.
Thanks,
David
next prev parent reply other threads:[~2015-08-16 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 19:58 Enabling and disabling maildir.synchronize_flags dm-list-email-notmuch
2015-08-16 9:39 ` David Bremner
2015-08-16 9:52 ` David Mazieres [this message]
2015-08-16 12:57 ` David Bremner
[not found] ` <87vbcf9ge1.fsf@ta.scs.stanford.edu>
2015-08-16 19:34 ` dm-list-email-notmuch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mjzblwc.fsf@ta.scs.stanford.edu \
--to=dm-list-email-notmuch@scs.stanford.edu \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).