Re: emacs: notmuch-tree, reading messages and tags
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 markwalters1...@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 m...@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 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [Patch v2 1/2] CLI: set up infrastructure to make path to gpg configurable.
David Bremner da...@tethera.net writes: GMIME takes a path to gpg, but we hardcode that path. In this commit we set up argument passing and option storage to allow this path to specified in the top level notmuch command. Pushed these two, with two trivial test fixes for the new variable. d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
emacs: notmuch-tree, reading messages and tags
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
Re: emacs: notmuch-tree, reading messages and tags
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 m...@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 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[Patch v2 1/2] CLI: set up infrastructure to make path to gpg configurable.
David Bremner writes: > GMIME takes a path to gpg, but we hardcode that path. In this commit > we set up argument passing and option storage to allow this path to > specified in the top level notmuch command. Pushed these two, with two trivial test fixes for the new variable. d
[PATCH 1/2] cli: fix top level --help combined with other options
Jani Nikula writes: > If the top level --help is combined with other options, help > fails. For example: > > $ notmuch --version --help > > Sorry, --help is not a known command. There's not much I can do to > help pushed these two
emacs: notmuch-tree, reading messages and tags
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
emacs: notmuch-tree, reading messages and tags
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 at notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch
emacs: notmuch-tree, reading messages and tags
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 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>
