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