Re: post-new [was: Re: query on a subset of messages ?]

diff --git a/61/ca1487d42f4e46c4a41eb2a102d3ab388cc8b2 b/61/ca1487d42f4e46c4a41eb2a102d3ab388cc8b2
new file mode 100644 (file)
index 0000000..f61dc8d
--- /dev/null
+++ b/61/ca1487d42f4e46c4a41eb2a102d3ab388cc8b2
@@ -0,0 +1,106 @@
+Return-Path: <sebastien.binet@cern.ch>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 1D40C431E82\r
+       for <notmuch@notmuchmail.org>; Tue, 10 Jul 2012 02:59:47 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -5\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-5 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_HI=-5] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id zoJcLtAR1VLE for <notmuch@notmuchmail.org>;\r
+       Tue, 10 Jul 2012 02:59:45 -0700 (PDT)\r
+Received: from CERNMX30.cern.ch (cernmx30.cern.ch [137.138.144.177])\r
+       (using TLSv1 with cipher AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 3BD22431E64\r
+       for <notmuch@notmuchmail.org>; Tue, 10 Jul 2012 02:59:45 -0700 (PDT)\r
+Received: from CERNFE22.cern.ch (137.138.144.151) by cernmxgwlb2.cern.ch\r
+       (137.138.144.177) with Microsoft SMTP Server (TLS) id 14.2.283.3;\r
+       Tue, 10 Jul 2012 11:59:40 +0200\r
+Received: from localhost (134.158.88.68) by smtp.cern.ch (137.138.144.172)\r
+       with Microsoft SMTP Server (TLS) id 14.2.298.4;\r
+       Tue, 10 Jul 2012 11:59:40 +0200\r
+From: Sebastien Binet <binet@cern.ch>\r
+To: Jani Nikula <jani@nikula.org>, Jameson Graef Rollins\r
+       <jrollins@finestructure.net>\r
+Subject: Re: post-new [was: Re: query on a subset of messages ?]\r
+In-Reply-To:\r
+ <CAB+hUn-=K20mSuAkptMXZvQNv+4Mvy7sT9tVxfdYXY8yb-euJw@mail.gmail.com>\r
+References: <871ukl5oj7.fsf@cern.ch> <87ehol2aku.fsf@servo.finestructure.net>\r
+       <87wr2c3mtj.fsf@cern.ch> <87r4sk3lxu.fsf@cern.ch>\r
+       <8739503llz.fsf@servo.finestructure.net>\r
+       <CAB+hUn-=K20mSuAkptMXZvQNv+4Mvy7sT9tVxfdYXY8yb-euJw@mail.gmail.com>\r
+User-Agent: Notmuch/0.13.2+60~g7ecf77d (http://notmuchmail.org) Emacs/24.1.1\r
+       (x86_64-unknown-linux-gnu)\r
+Date: Tue, 10 Jul 2012 11:59:39 +0200\r
+Message-ID: <871ukk2ayc.fsf@cern.ch>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1;\r
+       protocol="application/pgp-signature"\r
+X-Originating-IP: [134.158.88.68]\r
+Keywords: CERN SpamKiller Note: -50\r
+Cc: Notmuch Mail <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 10 Jul 2012 09:59:47 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+Jani Nikula <jani@nikula.org> writes:\r
+\r
+> On Jul 9, 2012 8:12 PM, "Jameson Graef Rollins" <jrollins@finestructure.net>\r
+> wrote:\r
+>>\r
+>> On Mon, Jul 09 2012, Sebastien Binet <binet@cern.ch> wrote:\r
+>> > hum... is post-new supposed to be run even if there is no new message ?\r
+>>\r
+>> Hi, Sebastian.  Yes, I think it runs regardless if there are any new\r
+>> messages or not.\r
+>\r
+> That's correct; only errors in notmuch new cause post-new hook to be\r
+> skipped.\r
+\r
+ok. I thought using the post-new hook would have saved some i/o\r
+resources over my current setup:\r
+ offlineimap.postsynchook = ~/emacs/notmuch-lib/notmuch-tag.sh\r
+\r
+where notmuch-tag.sh is (in pseudo-code):\r
+##\r
+/usr/bin/notmuch new\r
+\r
+for tag,query in tag-queries:\r
+  tag_new $tag $query\r
+\r
+##\r
+\r
+is there any advantage of using post-new compared to this setup ?\r
+\r
+-s\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v2.0.19 (GNU/Linux)\r
+\r
+iEYEARECAAYFAk/7/QsACgkQPj4AVbsZCCYG+ACgovkkfxC8rj63LxkD6iHbcS8a\r
+TeEAn3UDozbQ64b4b2tARvez3OxYGv3R\r
+=Rdqr\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r