56/8a8e5e11569cecaa803b78ee2dd1bccabf3119

   1 Return-Path: <jeremy@nickurak.ca>\r
   2 X-Original-To: notmuch@notmuchmail.org\r
   3 Delivered-To: notmuch@notmuchmail.org\r
   4 Received: from localhost (localhost [127.0.0.1])\r
   5         by olra.theworths.org (Postfix) with ESMTP id C5714431FAF\r
   6         for <notmuch@notmuchmail.org>; Wed, 28 Nov 2012 08:46:56 -0800 (PST)\r
   7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
   8 X-Spam-Flag: NO\r
   9 X-Spam-Score: -0.699\r
  10 X-Spam-Level: \r
  11 X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
  12         tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001,\r
  13         RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
  14 Received: from olra.theworths.org ([127.0.0.1])\r
  15         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
  16         with ESMTP id yPFsmHk4Gl0y for <notmuch@notmuchmail.org>;\r
  17         Wed, 28 Nov 2012 08:46:55 -0800 (PST)\r
  18 Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com\r
  19         [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
  20         (No client certificate requested)\r
  21         by olra.theworths.org (Postfix) with ESMTPS id C5E4C431FAE\r
  22         for <notmuch@notmuchmail.org>; Wed, 28 Nov 2012 08:46:54 -0800 (PST)\r
  23 Received: by mail-lb0-f181.google.com with SMTP id ge1so11560683lbb.26\r
  24         for <notmuch@notmuchmail.org>; Wed, 28 Nov 2012 08:46:53 -0800 (PST)\r
  25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
  26         d=nickurak.ca; s=google-dkim;\r
  27         h=mime-version:sender:x-originating-ip:in-reply-to:references:date\r
  28         :x-google-sender-auth:message-id:subject:from:to:content-type;\r
  29         bh=CMYJFpfRqZYARYdToqREEkiziommepK63U7Qqxphqk8=;\r
  30         b=YwiqIEYuxmGyBaQJ6JL//IbHWcukSfn/zYV218Bb7oNBrKMuUa+3NBzcjNsXCQSWto\r
  31         KM/nuw+h+VINCbCb4PpY5VYDL6BHWqfZyJLLPDFQhX8tntwaNB5lLzftCHolbZQ81iR7\r
  32         Up0MGWAeDmJ4c1jb4b78Fq4KKVinnjS8nXi9c=\r
  33 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
  34         d=google.com; s=20120113;\r
  35         h=mime-version:sender:x-originating-ip:in-reply-to:references:date\r
  36         :x-google-sender-auth:message-id:subject:from:to:content-type\r
  37         :x-gm-message-state;\r
  38         bh=CMYJFpfRqZYARYdToqREEkiziommepK63U7Qqxphqk8=;\r
  39         b=llxSmOLlv7p5yRUB/1NAVrsjXNOyro03UjRRw7E5+G+5kJ2qmBbN3PBVI/AzVzaKJd\r
  40         3RVyxRKrgyLJmzsDiBm6BLGMaIZ8JQG/4dEDZ92ja1S+9BX1P8UQEfnejVnoykEmod06\r
  41         KvzMxmTf0nWXEXk0f13x9E+5lqtsqzCsDPSnaNqlejWpeJlFZz95POH3q/2KdA97phR7\r
  42         FMDIQgWaFUSUMdAW0/OnLiXctkmlDzXiX3yJl8TevYKlTvLE++qY+1+9UI600ce7qR+r\r
  43         oj6PlDUq39W5q9yKq9Y320IxmgiGCgYIIldmgJD+YaGSV3LikAYu0hZ3eTMN/muS0Hsm\r
  44         ijag==\r
  45 MIME-Version: 1.0\r
  46 Received: by 10.112.31.194 with SMTP id c2mr8066905lbi.44.1354121213189; Wed,\r
  47         28 Nov 2012 08:46:53 -0800 (PST)\r
  48 Sender: jeremy@nickurak.ca\r
  49 Received: by 10.114.37.71 with HTTP; Wed, 28 Nov 2012 08:46:52 -0800 (PST)\r
  50 X-Originating-IP: [68.148.28.35]\r
  51 In-Reply-To: <50B62409.7050706@gmail.com>\r
  52 References: <50B62409.7050706@gmail.com>\r
  53 Date: Wed, 28 Nov 2012 09:46:52 -0700\r
  54 X-Google-Sender-Auth: JMqwvr5hkSwYX_ZHK-kSft5QFcc\r
  55 Message-ID:\r
  56  <CA+eQo_0wOSjHoMK30_PwGZonBNbSDCRy+ghX-TnimfZp++8cBg@mail.gmail.com>\r
  57 Subject: Re: gmail label support in offlineimap - update\r
  58 From: Jeremy Nickurak <not-much@trk.nickurak.ca>\r
  59 To: notmuch <notmuch@notmuchmail.org>\r
  60 Content-Type: multipart/alternative; boundary=f46d04016951e51ed904cf90e9f9\r
  61 X-Gm-Message-State:\r
  62  ALoCoQmVZMgJjJUSerLFNArTGUWRbeSDshnoxcKRKdW4coI0nX/lTagNJbEW8TFvLJ9OEQhYGnVu\r
  63 X-BeenThere: notmuch@notmuchmail.org\r
  64 X-Mailman-Version: 2.1.13\r
  65 Precedence: list\r
  66 List-Id: "Use and development of the notmuch mail system."\r
  67         <notmuch.notmuchmail.org>\r
  68 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  69         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  70 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  71 List-Post: <mailto:notmuch@notmuchmail.org>\r
  72 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  73 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  74         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  75 X-List-Received-Date: Wed, 28 Nov 2012 16:46:56 -0000\r
  76 \r
  77 --f46d04016951e51ed904cf90e9f9\r
  78 Content-Type: text/plain; charset=UTF-8\r
  79 \r
  80 As far as syncing flags to notmuch, it sounds like this would be easy to\r
  81 achieve with an independent 3rd tool, or even a small script:\r
  82 1) Find files in the maildir modified since the last check\r
  83 2) Read their keywords headers\r
  84 3) Update the notmuch tags accordingnly.\r
  85 \r
  86 The other direction sounds like it would be trickier though, since there's\r
  87 no obvious way to say "what notmuch tags have changed since time X?". Is\r
  88 this something that notmuch could provide?\r
  89 \r
  90 Alternatively, would it be a good idea to give notmuch a tags-changed hook,\r
  91 so that an external tool could be called on a tag change? That sounds like\r
  92 would solve this problem, keep the gmail/imap logic safely away from\r
  93 notmuch, and probably provide some really interesting other opportunities\r
  94 for automation of things by tags.\r
  95 \r
  96 --f46d04016951e51ed904cf90e9f9\r
  97 Content-Type: text/html; charset=UTF-8\r
  98 Content-Transfer-Encoding: quoted-printable\r
  99 \r
 100 As far as syncing flags to notmuch, it sounds like this would be easy to ac=\r
 101 hieve with an independent 3rd tool, or even a small script:<div>1) Find fil=\r
 102 es in the maildir modified since the last check</div><div>2) Read their key=\r
 103 words headers</div>\r
 104 \r
 105 <div>3) Update the notmuch tags accordingnly.</div><div><br></div><div>The =\r
 106 other direction sounds like it would be trickier though, since there&#39;s =\r
 107 no obvious way to say &quot;what notmuch tags have changed since time X?&qu=\r
 108 ot;. Is this something that notmuch could provide?</div>\r
 109 <div><br></div><div>Alternatively, would it be a good idea to give notmuch =\r
 110 a tags-changed hook, so that an external tool could be called on a tag chan=\r
 111 ge? That sounds like would solve this problem, keep the gmail/imap logic sa=\r
 112 fely away from notmuch, and probably provide some really interesting other =\r
 113 opportunities for automation of things by tags.</div>\r
 114 \r
 115 \r
 116 --f46d04016951e51ed904cf90e9f9--\r