From: Johan Parin <johanparin@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: Unread handling
Date: Tue, 12 Nov 2019 19:45:24 +0100 [thread overview]
Message-ID: <m2sgmtj5mj.fsf@gmail.com> (raw)
In-Reply-To: <87o8xi1k3q.fsf@iki.fi> (Teemu Likonen's message of "Mon, 11 Nov 2019 17:57:45 +0200")
Teemu Likonen <tlikonen@iki.fi> writes:
>
> It seems to me that using search term tag:unread will help you. Try this
> in the *hello* buffer:
>
> z tag:unread
>
> You'll go directly to tree view and unread messages will show with
> normal colours and read messages with grey colour. Commands "n" and
> "p" will skip over read messages ("N" and "P" won't). You can
> configure saved searches to start with tree view.
Yes this is very good. Actually what I do now is
s tag:unread date:-2d..
which gives me almost what I want. Only downside is, completely unread
threads don't show up in the search view. Sometimes I want to go back
and read a read thread. But this can be solved by using flagged (or some
other tag). So now I have:
s ((tag:unread date:-2d..) or tag:flagged)
which works pretty well.
Thanks!
/Johan
prev parent reply other threads:[~2019-11-12 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 23:16 Unread handling Johan Parin
2019-11-11 8:14 ` David Edmondson
2019-11-12 13:17 ` William Casarin
2019-11-12 13:35 ` David Edmondson
2019-11-12 14:01 ` William Casarin
2019-11-12 13:53 ` Teemu Likonen
2019-11-12 13:59 ` William Casarin
2019-11-12 14:54 ` Teemu Likonen
2019-11-12 15:11 ` Teemu Likonen
2019-11-12 15:58 ` William Casarin
2019-11-11 15:57 ` Teemu Likonen
2019-11-12 18:45 ` Johan Parin [this message]
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=m2sgmtj5mj.fsf@gmail.com \
--to=johanparin@gmail.com \
--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).