From: Mark Walters <markwalters1009@gmail.com>
To: matt@bubblegen.co.uk, notmuch@notmuchmail.org
Subject: Re: emacs: notmuch-tree, reading messages and tags
Date: Wed, 11 Mar 2015 13:52:57 +0000 [thread overview]
Message-ID: <87sidbej46.fsf@qmul.ac.uk> (raw)
In-Reply-To: <97881ceaba7c5057e21676c4102c5c7d.squirrel@webmail.plus.net>
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 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
next prev parent reply other threads:[~2015-03-11 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 12:22 emacs: notmuch-tree, reading messages and tags Matthew Lear
2015-03-11 13:52 ` Mark Walters [this message]
2015-03-11 15:42 ` Matthew Lear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sidbej46.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--cc=matt@bubblegen.co.uk \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).