1 Return-Path: <prvs=028810603=jrosenthal@jhu.edu>
\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 4A170431FBF
\r
6 for <notmuch@notmuchmail.org>; Tue, 19 Nov 2013 05:46:41 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id dmDH5GSRCr9b for <notmuch@notmuchmail.org>;
\r
16 Tue, 19 Nov 2013 05:46:33 -0800 (PST)
\r
17 Received: from smtpauth.johnshopkins.edu (smtpauth.johnshopkins.edu
\r
18 [162.129.8.150]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 7A729431FBC
\r
21 for <notmuch@notmuchmail.org>; Tue, 19 Nov 2013 05:46:33 -0800 (PST)
\r
22 X-IronPort-AV: E=Sophos;i="4.93,729,1378872000";
\r
23 d="scan'208";a="8639971"
\r
24 Received: from c-69-137-43-192.hsd1.md.comcast.net (HELO localhost)
\r
26 by ipex0.johnshopkins.edu with ESMTP/TLS/DHE-RSA-AES256-SHA;
\r
27 19 Nov 2013 08:46:28 -0500
\r
28 From: Jesse Rosenthal <jrosenthal@jhu.edu>
\r
29 To: Tomi Valkeinen <tomi.valkeinen@iki.fi>, Jani Nikula <jani@nikula.org>,
\r
30 notmuch@notmuchmail.org
\r
31 Subject: Re: notmuch-lib questions and observations
\r
32 In-Reply-To: <528B5C1F.4050908@iki.fi>
\r
33 References: <528A26F4.3040006@iki.fi> <87bo1gio9c.fsf@nikula.org>
\r
34 <528B5C1F.4050908@iki.fi>
\r
35 User-Agent: Notmuch/0.16+156~gdb5189a (http://notmuchmail.org) Emacs/24.3.1
\r
36 (x86_64-apple-darwin)
\r
37 Date: Tue, 19 Nov 2013 08:46:24 -0500
\r
38 Message-ID: <m161rofqrz.fsf@jhu.edu>
\r
40 Content-Type: text/plain
\r
41 X-BeenThere: notmuch@notmuchmail.org
\r
42 X-Mailman-Version: 2.1.13
\r
44 List-Id: "Use and development of the notmuch mail system."
\r
45 <notmuch.notmuchmail.org>
\r
46 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
47 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
48 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
49 List-Post: <mailto:notmuch@notmuchmail.org>
\r
50 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
51 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
52 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
53 X-List-Received-Date: Tue, 19 Nov 2013 13:46:41 -0000
\r
55 Tomi Valkeinen <tomi.valkeinen@iki.fi> writes:
\r
57 > I think I wasn't very clear on what I meant. I was thinking about the
\r
58 > behavior that graphical mail clients have: they periodically refresh the
\r
59 > emails, showing new ones if there are any, and they'll show some icon or
\r
60 > such which tells the user this email is "new" (which could mean received
\r
61 > in the last periodic refresh).
\r
63 I do something similar to what you were describing. I put two tags,
\r
64 "fresh" and "new" on mails that have just come in. "fresh" is for
\r
65 internal use -- it allows me to run scripts on certain mails that
\r
66 haven't been checked before, and it is taken off of everything before I
\r
67 see it. "new" is left on, and means that it just came in with the last
\r
68 poll. This is all done as a post-new hook. Then, as pre-new hook, I
\r
69 remove all the "new" tags. So when I poll again, I only see the ones
\r
70 that came in with the newest poll.
\r
72 If I want to see what I've received since the last poll, I just run a
\r
73 search with "tag:new AND tag:inbox."
\r
75 Now, this is dones with the hooks that the command-line client uses, so
\r
76 you'd have to implement it yourself for your client, but that shouldn't
\r