emacs: notmuch-tree, reading messages and tags

[Matthew Lear]

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 at 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 at 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
>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 at notmuchmail.org
>> http://notmuchmail.org/mailman/listinfo/notmuch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20150311/92fe2f48/attachment.html>