MIME-Version: 1.0
Sender: jeremy@nickurak.ca
In-Reply-To: <50B62409.7050706@gmail.com>
References: <50B62409.7050706@gmail.com>
Date: Wed, 28 Nov 2012 09:46:52 -0700
Message-ID:
 <CA+eQo_0wOSjHoMK30_PwGZonBNbSDCRy+ghX-TnimfZp++8cBg@mail.gmail.com>
Subject: Re: gmail label support in offlineimap - update
From: Jeremy Nickurak <not-much@trk.nickurak.ca>
To: notmuch <notmuch@notmuchmail.org>
Content-Type: multipart/alternative; boundary=f46d04016951e51ed904cf90e9f9
Precedence: list

--f46d04016951e51ed904cf90e9f9
Content-Type: text/plain; charset=UTF-8

As far as syncing flags to notmuch, it sounds like this would be easy to
achieve with an independent 3rd tool, or even a small script:
1) Find files in the maildir modified since the last check
2) Read their keywords headers
3) Update the notmuch tags accordingnly.

The other direction sounds like it would be trickier though, since there's
no obvious way to say "what notmuch tags have changed since time X?". Is
this something that notmuch could provide?

Alternatively, would it be a good idea to give notmuch a tags-changed hook,
so that an external tool could be called on a tag change? That sounds like
would solve this problem, keep the gmail/imap logic safely away from
notmuch, and probably provide some really interesting other opportunities
for automation of things by tags.

--f46d04016951e51ed904cf90e9f9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

As far as syncing flags to notmuch, it sounds like this would be easy to ac=
hieve with an independent 3rd tool, or even a small script:<div>1) Find fil=
es in the maildir modified since the last check</div><div>2) Read their key=
words headers</div>

<div>3) Update the notmuch tags accordingnly.</div><div><br></div><div>The =
other direction sounds like it would be trickier though, since there&#39;s =
no obvious way to say &quot;what notmuch tags have changed since time X?&qu=
ot;. Is this something that notmuch could provide?</div>
<div><br></div><div>Alternatively, would it be a good idea to give notmuch =
a tags-changed hook, so that an external tool could be called on a tag chan=
ge? That sounds like would solve this problem, keep the gmail/imap logic sa=
fely away from notmuch, and probably provide some really interesting other =
opportunities for automation of things by tags.</div>


--f46d04016951e51ed904cf90e9f9--