On Sat, 05 Oct 2013, Austin Clements wrote:
> One of the problems with the current approach, which most of these
> options share, is that there's no feedback. For example, when I enter
> a thread, I have no idea if the first message was unread or not.
Agreed. And this gets repeated for
On Sat, 05 Oct 2013, Austin Clements amdra...@mit.edu wrote:
One of the problems with the current approach, which most of these
options share, is that there's no feedback. For example, when I enter
a thread, I have no idea if the first message was unread or not.
Agreed. And this gets repeated
On Sat, 05 Oct 2013, Austin Clements wrote:
> Great list.
>
> One of the problems with the current approach, which most of these
> options share, is that there's no feedback. For example, when I enter
> a thread, I have no idea if the first message was unread or not. I'd
> like a solution that
Great list.
One of the problems with the current approach, which most of these
options share, is that there's no feedback. For example, when I enter
a thread, I have no idea if the first message was unread or not. I'd
like a solution that either naturally doesn't have this problem, that
Hello
I agree that the unread tag does not work well. There are some instances
which I would class as plain bugs (notmuch-show-next-message which is
bound to N marks the new message read even if it is collapsed) and
other instances where it is not clear what the correct behaviour should
be.
I
Hello
I agree that the unread tag does not work well. There are some instances
which I would class as plain bugs (notmuch-show-next-message which is
bound to N marks the new message read even if it is collapsed) and
other instances where it is not clear what the correct behaviour should
be.
I
Great list.
One of the problems with the current approach, which most of these
options share, is that there's no feedback. For example, when I enter
a thread, I have no idea if the first message was unread or not. I'd
like a solution that either naturally doesn't have this problem, that
On Sat, 05 Oct 2013, Austin Clements amdra...@mit.edu wrote:
Great list.
One of the problems with the current approach, which most of these
options share, is that there's no feedback. For example, when I enter
a thread, I have no idea if the first message was unread or not. I'd
like a
On Wed, Sep 18 2013, Gregor Zattler wrote:
> This seems strange to me. I would say the unread tag should be
> removed when leaving the message with the last press on space
> bar, indicating that one really paged trough the whole message
> instead of only seeing the very beginning of it.
>
>
Dear notmuchers,
I had difficulties to reliably remove the "unread" tag from
messages. Mostly I page through threads with the space bar and
all is well. But when the beginning of the thread is already
collapsed and I "jump" in the middle of a message pressing space
bar does not remove the
Dear notmuchers,
I had difficulties to reliably remove the unread tag from
messages. Mostly I page through threads with the space bar and
all is well. But when the beginning of the thread is already
collapsed and I jump in the middle of a message pressing space
bar does not remove the unread
11 matches
Mail list logo