Re: emacs: notmuch-tree, reading messages and tags

diff --git a/a3/f67066f904669a6143bfaaf1e6229494817976 b/a3/f67066f904669a6143bfaaf1e6229494817976
new file mode 100644 (file)
index 0000000..7a153d3
--- /dev/null
+++ b/a3/f67066f904669a6143bfaaf1e6229494817976
@@ -0,0 +1,125 @@
+Return-Path: <matt@bubblegen.co.uk>\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 A171C431FBF\r
+       for <notmuch@notmuchmail.org>; Wed, 11 Mar 2015 08:42:16 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 2.439\r
+X-Spam-Level: **\r
+X-Spam-Status: No, score=2.439 tagged_above=-999 required=5\r
+       tests=[DNS_FROM_AHBL_RHSBL=2.438, HTML_MESSAGE=0.001]\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 PXcpMJPJybUI for <notmuch@notmuchmail.org>;\r
+       Wed, 11 Mar 2015 08:42:13 -0700 (PDT)\r
+Received: from sip.bubblegen.co.uk (bubblegen.plus.com [80.229.236.194])\r
+       (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 2F69D431FBC\r
+       for <notmuch@notmuchmail.org>; Wed, 11 Mar 2015 08:42:13 -0700 (PDT)\r
+In-Reply-To: <87sidbej46.fsf@qmul.ac.uk>\r
+References: <97881ceaba7c5057e21676c4102c5c7d.squirrel@webmail.plus.net>\r
+       <87sidbej46.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/alternative;\r
+       boundary="----OS94NOA7SYZ13JU3C9UEGEOY4HVTHG"\r
+Content-Transfer-Encoding: 8bit\r
+Subject: Re: emacs: notmuch-tree, reading messages and tags\r
+From: Matthew Lear <matt@bubblegen.co.uk>\r
+Date: Wed, 11 Mar 2015 15:42:07 +0000\r
+To: Mark Walters <markwalters1009@gmail.com>,notmuch@notmuchmail.org\r
+Message-ID: <D1648E3B-C0EE-4410-982C-B751AAF7E3A2@bubblegen.co.uk>\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: Wed, 11 Mar 2015 15:42:16 -0000\r
+\r
+------OS94NOA7SYZ13JU3C9UEGEOY4HVTHG\r
+Content-Transfer-Encoding: 8bit\r
+Content-Type: text/plain;\r
+ charset=UTF-8\r
+\r
+Hi Mark, \r
+That would be great. Yes b and space are useful but even navigating using them doesn't clear the unread flag in the message pane so refreshing the notmuch-tree view still shows the message(s) as unread. \r
+I'll keep an eye on git for the changes going in. \r
+Cheers, \r
+ Matt \r
+\r
+On 11 March 2015 13:52:57 GMT+00:00, Mark Walters <markwalters1009@gmail.com> wrote:\r
+>\r
+>Hi\r
+>\r
+>I think that is a bug (my fault) which happened when the unread tag\r
+>handling went in. I will try and fix it.\r
+>\r
+>Incidentally you can scroll the message pane with space and b without\r
+>having to switch frames.\r
+>\r
+>Best wishes\r
+>\r
+>Mark\r
+>\r
+>On Wed, 11 Mar 2015, Matthew Lear <matt@bubblegen.co.uk> wrote:\r
+>> Hi,\r
+>> If I switch to viewing a thread with notmuch-tree, I can navigate\r
+>through,\r
+>> and read messages using up/down + RET just fine. Each message is\r
+>shown in\r
+>> a seperate window. However, if point never enters that message\r
+>window, the\r
+>> unread tag is removed (strikethrough) from the message in the\r
+>notmuch-tree\r
+>> view but not from the message in the message window itself. If I\r
+>refresh\r
+>> the notmuch tree view, all messages still have their unread tag\r
+>applied.\r
+>>\r
+>> The only time that the unread tag is removed is if point enters the\r
+>> message window. For messages that are only a few lines long (eg a\r
+>reply to\r
+>> the previous message in the thread is only a few lines) and which can\r
+>be\r
+>> read without putting point in the message window to scroll, having to\r
+>> specifically select the message window in order for the unread tag to\r
+>be\r
+>> removed from the message seems totally unnecessary and is\r
+>inconvenient.\r
+>>\r
+>> Is this by design or am I using it wrongly? Is this behaviour\r
+>configurable?\r
+>>\r
+>> Cheers,\r
+>> --  Matt\r
+>>\r
+>> _______________________________________________\r
+>> notmuch mailing list\r
+>> notmuch@notmuchmail.org\r
+>> http://notmuchmail.org/mailman/listinfo/notmuch\r
+\r
+------OS94NOA7SYZ13JU3C9UEGEOY4HVTHG\r
+Content-Type: text/html;\r
+ charset=utf-8\r
+Content-Transfer-Encoding: 8bit\r
+\r
+<html><head></head><body>Hi Mark, <br>\r
+That would be great. Yes b and space are useful but even navigating using them doesn&#39;t clear the unread flag in the message pane so refreshing the notmuch-tree view still shows the message(s) as unread. <br>\r
+I&#39;ll keep an eye on git for the changes going in. <br>\r
+Cheers, <br>\r
+ Matt <br><br><div class="gmail_quote">On 11 March 2015 13:52:57 GMT+00:00, Mark Walters &lt;markwalters1009@gmail.com&gt; wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">\r
+<pre class="k9mail"><br />Hi<br /><br />I think that is a bug (my fault) which happened when the unread tag<br />handling went in. I will try and fix it.<br /><br />Incidentally you can scroll the message pane with space and b without<br />having to switch frames.<br /><br />Best wishes<br /><br />Mark<br /><br />On Wed, 11 Mar 2015, Matthew Lear &lt;matt@bubblegen.co.uk&gt; wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Hi,<br /> If I switch to viewing a thread with notmuch-tree, I can navigate through,<br /> and read messages using up/down + RET just fine. Each message is shown in<br /> a seperate window. However, if point never enters that message window, the<br /> unread tag is removed (strikethrough) from the message in the notmuch-tree<br /> view but not from the message in the message window itself. If I refresh<br /> the notmuch tree view, all messages still have their unread tag appli\r
+ ed.<br\r
+/><br /> The only time that the unread tag is removed is if point enters the<br /> message window. For messages that are only a few lines long (eg a reply to<br /> the previous message in the thread is only a few lines) and which can be<br /> read without putting point in the message window to scroll, having to<br /> specifically select the message window in order for the unread tag to be<br /> removed from the message seems totally unnecessary and is inconvenient.<br /><br /> Is this by design or am I using it wrongly? Is this behaviour configurable?<br /><br /> Cheers,<br /> --  Matt<br /><br /><hr /><br /> notmuch mailing list<br /> notmuch@notmuchmail.org<br /> <a href="http://notmuchmail.org/mailman/listinfo/notmuch">http://notmuchmail.org/mailman/listinfo/notmuch</a><br /></blockquote></pre></blockquote></div></body></html>\r
+------OS94NOA7SYZ13JU3C9UEGEOY4HVTHG--\r
+\r