From: "Sebastian Spaeth" <Sebastian@SSpaeth.de>
To: notmuch@notmuchmail.org
In-Reply-To: <20100119160449.GA28198@finestructure.net>
References: <87pr57jvkz.fsf@SSpaeth.de>
	<201001181641.25647.sojkam1@fel.cvut.cz> <87hbqjwgmf.fsf@SSpaeth.de>
	<87my0a5i80.fsf@SSpaeth.de> <87my0aqgw9.fsf@veldthuis.com>
	<20100119152427.GL8342@finestructure.net> <877hrexfat.fsf@SSpaeth.de>
	<20100119160449.GA28198@finestructure.net>
Date: Tue, 19 Jan 2010 17:13:44 +0100
Message-ID: <87636yxebr.fsf@SSpaeth.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] Introducing notmuchsync
Precedence: list

On Tue, 19 Jan 2010 11:04:49 -0500, Jameson Rollins <jrollins@finestructure.net> wrote:
> I should have mentioned in my previous mail that I think this tool is
> a great idea, and I plan on using it.  I just hope that all of it's
> functionality will be integrated directly into notmuch itself.

I fully agree. 
[Snip more stuff I fully agree with]
[snip workflow]

> Do you do another notmuchsync after the final notmuch new, to get any
> new flags in the maildir synced with the database?

Ohh, I had never considered that, but true, if another mail client
modifies maildir flags, we probably want to have that reflected as notmuch
tags as well...

So, yes that should work even better (my real script is a bit fancier,
changing output options ans stuff):

notmuch new       # make db consistent (earlier deleted mails etc)
notmuchsync -s -n # MailDir flags update and "cur" dir moving
offlineimap       # sync with IMAP server
notmuch new       # incorporate new mails in notmuch db
notmuchsync -r -n # reflect changed MailDir flags in notmuch tags

Sorry for all the spam today about my toys. I'll try to keep a bit
more quiet in the future in order to not start annoying you. :-)

spaetz