From: Jeremy Nickurak Date: Wed, 28 Nov 2012 16:46:52 +0000 (+1700) Subject: Re: gmail label support in offlineimap - update X-Git-Url: http://git.tremily.us/gitweb.cgi?a=commitdiff_plain;h=f1d6a3d6e451ea2c84a6c1a53ad962a616105eb5;p=notmuch-archives.git Re: gmail label support in offlineimap - update --- diff --git a/56/8a8e5e11569cecaa803b78ee2dd1bccabf3119 b/56/8a8e5e11569cecaa803b78ee2dd1bccabf3119 new file mode 100644 index 000000000..cfa35ac5c --- /dev/null +++ b/56/8a8e5e11569cecaa803b78ee2dd1bccabf3119 @@ -0,0 +1,116 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id C5714431FAF + for ; Wed, 28 Nov 2012 08:46:56 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.699 +X-Spam-Level: +X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 + tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, + RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id yPFsmHk4Gl0y for ; + Wed, 28 Nov 2012 08:46:55 -0800 (PST) +Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com + [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id C5E4C431FAE + for ; Wed, 28 Nov 2012 08:46:54 -0800 (PST) +Received: by mail-lb0-f181.google.com with SMTP id ge1so11560683lbb.26 + for ; Wed, 28 Nov 2012 08:46:53 -0800 (PST) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=nickurak.ca; s=google-dkim; + h=mime-version:sender:x-originating-ip:in-reply-to:references:date + :x-google-sender-auth:message-id:subject:from:to:content-type; + bh=CMYJFpfRqZYARYdToqREEkiziommepK63U7Qqxphqk8=; + b=YwiqIEYuxmGyBaQJ6JL//IbHWcukSfn/zYV218Bb7oNBrKMuUa+3NBzcjNsXCQSWto + KM/nuw+h+VINCbCb4PpY5VYDL6BHWqfZyJLLPDFQhX8tntwaNB5lLzftCHolbZQ81iR7 + Up0MGWAeDmJ4c1jb4b78Fq4KKVinnjS8nXi9c= +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=google.com; s=20120113; + h=mime-version:sender:x-originating-ip:in-reply-to:references:date + :x-google-sender-auth:message-id:subject:from:to:content-type + :x-gm-message-state; + bh=CMYJFpfRqZYARYdToqREEkiziommepK63U7Qqxphqk8=; + b=llxSmOLlv7p5yRUB/1NAVrsjXNOyro03UjRRw7E5+G+5kJ2qmBbN3PBVI/AzVzaKJd + 3RVyxRKrgyLJmzsDiBm6BLGMaIZ8JQG/4dEDZ92ja1S+9BX1P8UQEfnejVnoykEmod06 + KvzMxmTf0nWXEXk0f13x9E+5lqtsqzCsDPSnaNqlejWpeJlFZz95POH3q/2KdA97phR7 + FMDIQgWaFUSUMdAW0/OnLiXctkmlDzXiX3yJl8TevYKlTvLE++qY+1+9UI600ce7qR+r + oj6PlDUq39W5q9yKq9Y320IxmgiGCgYIIldmgJD+YaGSV3LikAYu0hZ3eTMN/muS0Hsm + ijag== +MIME-Version: 1.0 +Received: by 10.112.31.194 with SMTP id c2mr8066905lbi.44.1354121213189; Wed, + 28 Nov 2012 08:46:53 -0800 (PST) +Sender: jeremy@nickurak.ca +Received: by 10.114.37.71 with HTTP; Wed, 28 Nov 2012 08:46:52 -0800 (PST) +X-Originating-IP: [68.148.28.35] +In-Reply-To: <50B62409.7050706@gmail.com> +References: <50B62409.7050706@gmail.com> +Date: Wed, 28 Nov 2012 09:46:52 -0700 +X-Google-Sender-Auth: JMqwvr5hkSwYX_ZHK-kSft5QFcc +Message-ID: + +Subject: Re: gmail label support in offlineimap - update +From: Jeremy Nickurak +To: notmuch +Content-Type: multipart/alternative; boundary=f46d04016951e51ed904cf90e9f9 +X-Gm-Message-State: + ALoCoQmVZMgJjJUSerLFNArTGUWRbeSDshnoxcKRKdW4coI0nX/lTagNJbEW8TFvLJ9OEQhYGnVu +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Wed, 28 Nov 2012 16:46:56 -0000 + +--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:
1) Find fil= +es in the maildir modified since the last check
2) Read their key= +words 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?&qu= +ot;. 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 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.
+ + +--f46d04016951e51ed904cf90e9f9--