From: Teemu Likonen <tlikonen@iki.fi>
To: Johan Parin <johanparin@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Unread handling
Date: Mon, 11 Nov 2019 17:57:45 +0200 [thread overview]
Message-ID: <87o8xi1k3q.fsf@iki.fi> (raw)
In-Reply-To: <m2zhh3jpa6.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
Johan Parin [2019-11-11T00:16:17+01] wrote:
> My real frustration lies in the thread view. Typically threads will be
> partially read and I want to read only unread messages.
> I'm trying instead to use the tree view, this seems to me the more
> natural way to view threads. So I immediately do `Z' whenever I enter
> a thread. I would like to have the option to enter tree view
> automatically for a thread from the search buffer. Is it possible?
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.
--
/// OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450
// https://keys.openpgp.org/search?q=tlikonen@iki.fi
/ https://keybase.io/tlikonen https://github.com/tlikonen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 694 bytes --]
next prev parent reply other threads:[~2019-11-11 16:40 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 [this message]
2019-11-12 18:45 ` Johan Parin
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=87o8xi1k3q.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=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).