Re: notmuch-lib questions and observations

diff --git a/38/17716a1c98abedad66e0bbebd2287cb46c0833 b/38/17716a1c98abedad66e0bbebd2287cb46c0833
new file mode 100644 (file)
index 0000000..bd0808e
--- /dev/null
+++ b/38/17716a1c98abedad66e0bbebd2287cb46c0833
@@ -0,0 +1,79 @@
+Return-Path: <prvs=028810603=jrosenthal@jhu.edu>\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 4A170431FBF\r
+       for <notmuch@notmuchmail.org>; Tue, 19 Nov 2013 05:46:41 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       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 dmDH5GSRCr9b for <notmuch@notmuchmail.org>;\r
+       Tue, 19 Nov 2013 05:46:33 -0800 (PST)\r
+Received: from smtpauth.johnshopkins.edu (smtpauth.johnshopkins.edu\r
+       [162.129.8.150]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 7A729431FBC\r
+       for <notmuch@notmuchmail.org>; Tue, 19 Nov 2013 05:46:33 -0800 (PST)\r
+X-IronPort-AV: E=Sophos;i="4.93,729,1378872000"; \r
+   d="scan'208";a="8639971"\r
+Received: from c-69-137-43-192.hsd1.md.comcast.net (HELO localhost)\r
+       ([69.137.43.192])\r
+       by ipex0.johnshopkins.edu with ESMTP/TLS/DHE-RSA-AES256-SHA;\r
+       19 Nov 2013 08:46:28 -0500\r
+From: Jesse Rosenthal <jrosenthal@jhu.edu>\r
+To: Tomi Valkeinen <tomi.valkeinen@iki.fi>, Jani Nikula <jani@nikula.org>,\r
+       notmuch@notmuchmail.org\r
+Subject: Re: notmuch-lib questions and observations\r
+In-Reply-To: <528B5C1F.4050908@iki.fi>\r
+References: <528A26F4.3040006@iki.fi> <87bo1gio9c.fsf@nikula.org>\r
+       <528B5C1F.4050908@iki.fi>\r
+User-Agent: Notmuch/0.16+156~gdb5189a (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-apple-darwin)\r
+Date: Tue, 19 Nov 2013 08:46:24 -0500\r
+Message-ID: <m161rofqrz.fsf@jhu.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\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, 19 Nov 2013 13:46:41 -0000\r
+\r
+Tomi Valkeinen <tomi.valkeinen@iki.fi> writes:\r
+\r
+> I think I wasn't very clear on what I meant. I was thinking about the\r
+> behavior that graphical mail clients have: they periodically refresh the\r
+> emails, showing new ones if there are any, and they'll show some icon or\r
+> such which tells the user this email is "new" (which could mean received\r
+> in the last periodic refresh).\r
+\r
+I do something similar to what you were describing. I put two tags,\r
+"fresh" and "new" on mails that have just come in. "fresh" is for\r
+internal use -- it allows me to run scripts on certain mails that\r
+haven't been checked before, and it is taken off of everything before I\r
+see it. "new" is left on, and means that it just came in with the last\r
+poll. This is all done as a post-new hook. Then, as  pre-new hook, I\r
+remove all the "new" tags. So when I poll again, I only see the ones\r
+that came in with the newest poll.\r
+\r
+If I want to see what I've received since the last poll, I just run a\r
+search with "tag:new AND tag:inbox."\r
+\r
+Now, this is dones with the hooks that the command-line client uses, so\r
+you'd have to implement it yourself for your client, but that shouldn't\r
+be too hard.\r
+\r
+\r