From: Matthew Lear Date: Wed, 11 Mar 2015 15:42:07 +0000 (+0000) Subject: Re: emacs: notmuch-tree, reading messages and tags X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=d4c9c6798c6d4665060a72997966e588a6fdcd15;p=notmuch-archives.git Re: emacs: notmuch-tree, reading messages and tags --- diff --git a/a3/f67066f904669a6143bfaaf1e6229494817976 b/a3/f67066f904669a6143bfaaf1e6229494817976 new file mode 100644 index 000000000..7a153d30e --- /dev/null +++ b/a3/f67066f904669a6143bfaaf1e6229494817976 @@ -0,0 +1,125 @@ +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 A171C431FBF + for ; Wed, 11 Mar 2015 08:42:16 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 2.439 +X-Spam-Level: ** +X-Spam-Status: No, score=2.439 tagged_above=-999 required=5 + tests=[DNS_FROM_AHBL_RHSBL=2.438, HTML_MESSAGE=0.001] + 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 PXcpMJPJybUI for ; + Wed, 11 Mar 2015 08:42:13 -0700 (PDT) +Received: from sip.bubblegen.co.uk (bubblegen.plus.com [80.229.236.194]) + (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 2F69D431FBC + for ; Wed, 11 Mar 2015 08:42:13 -0700 (PDT) +In-Reply-To: <87sidbej46.fsf@qmul.ac.uk> +References: <97881ceaba7c5057e21676c4102c5c7d.squirrel@webmail.plus.net> + <87sidbej46.fsf@qmul.ac.uk> +MIME-Version: 1.0 +Content-Type: multipart/alternative; + boundary="----OS94NOA7SYZ13JU3C9UEGEOY4HVTHG" +Content-Transfer-Encoding: 8bit +Subject: Re: emacs: notmuch-tree, reading messages and tags +From: Matthew Lear +Date: Wed, 11 Mar 2015 15:42:07 +0000 +To: Mark Walters ,notmuch@notmuchmail.org +Message-ID: +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: Wed, 11 Mar 2015 15:42:16 -0000 + +------OS94NOA7SYZ13JU3C9UEGEOY4HVTHG +Content-Transfer-Encoding: 8bit +Content-Type: text/plain; + charset=UTF-8 + +Hi Mark, +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. +I'll keep an eye on git for the changes going in. +Cheers, + Matt + +On 11 March 2015 13:52:57 GMT+00:00, Mark Walters wrote: +> +>Hi +> +>I think that is a bug (my fault) which happened when the unread tag +>handling went in. I will try and fix it. +> +>Incidentally you can scroll the message pane with space and b without +>having to switch frames. +> +>Best wishes +> +>Mark +> +>On Wed, 11 Mar 2015, Matthew Lear wrote: +>> Hi, +>> If I switch to viewing a thread with notmuch-tree, I can navigate +>through, +>> and read messages using up/down + RET just fine. Each message is +>shown in +>> a seperate window. However, if point never enters that message +>window, the +>> unread tag is removed (strikethrough) from the message in the +>notmuch-tree +>> view but not from the message in the message window itself. If I +>refresh +>> the notmuch tree view, all messages still have their unread tag +>applied. +>> +>> The only time that the unread tag is removed is if point enters the +>> message window. For messages that are only a few lines long (eg a +>reply to +>> the previous message in the thread is only a few lines) and which can +>be +>> read without putting point in the message window to scroll, having to +>> specifically select the message window in order for the unread tag to +>be +>> removed from the message seems totally unnecessary and is +>inconvenient. +>> +>> Is this by design or am I using it wrongly? Is this behaviour +>configurable? +>> +>> Cheers, +>> -- Matt +>> +>> _______________________________________________ +>> notmuch mailing list +>> notmuch@notmuchmail.org +>> http://notmuchmail.org/mailman/listinfo/notmuch + +------OS94NOA7SYZ13JU3C9UEGEOY4HVTHG +Content-Type: text/html; + charset=utf-8 +Content-Transfer-Encoding: 8bit + +Hi Mark,
+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.
+I'll keep an eye on git for the changes going in.
+Cheers,
+ Matt

On 11 March 2015 13:52:57 GMT+00:00, Mark Walters <markwalters1009@gmail.com> wrote:
+

Hi

I think that is a bug (my fault) which happened when the unread tag
handling went in. I will try and fix it.

Incidentally you can scroll the message pane with space and b without
having to switch frames.

Best wishes

Mark

On Wed, 11 Mar 2015, Matthew Lear <matt@bubblegen.co.uk> wrote:
Hi,
If I switch to viewing a thread with notmuch-tree, I can navigate through,
and read messages using up/down + RET just fine. Each message is shown in
a seperate window. However, if point never enters that message window, the
unread tag is removed (strikethrough) from the message in the notmuch-tree
view but not from the message in the message window itself. If I refresh
the notmuch tree view, all messages still have their unread tag appli + ed.

The only time that the unread tag is removed is if point enters the
message window. For messages that are only a few lines long (eg a reply to
the previous message in the thread is only a few lines) and which can be
read without putting point in the message window to scroll, having to
specifically select the message window in order for the unread tag to be
removed from the message seems totally unnecessary and is inconvenient.

Is this by design or am I using it wrongly? Is this behaviour configurable?

Cheers,
-- Matt



notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
+------OS94NOA7SYZ13JU3C9UEGEOY4HVTHG-- +