unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: William Casarin <jb55@jb55.com>
To: David Edmondson <dme@dme.org>, Johan Parin <johanparin@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Unread handling
Date: Tue, 12 Nov 2019 06:01:08 -0800	[thread overview]
Message-ID: <87woc5urbv.fsf@jb55.com> (raw)
In-Reply-To: <m2imnpqktr.fsf@dme.org>

David Edmondson <dme@dme.org> writes:

> On Tuesday, 2019-11-12 at 05:17:46 -08, William Casarin wrote: 
>
>> David Edmondson <dme@dme.org> writes: 
>>> On Monday, 2019-11-11 at 00:16:17 +01, Johan Parin wrote:  
>>>> 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?  
>>> 
>>> “Z” in search mode should take you directly to tree mode. 
>> 
>> true, but it opens tree mode for the entire search result. I 
>> find myself doing `c i z Ctrl-v` to open the tree view for a 
>> specific thread, but perhaps it would make sense if there was a 
>> default keybind for this. 
>
> Hmm, yes, that's a bit annoying.
>
> I'd suggest 'z' as a good binding, but obviously it's already 
> used. What would make sense?

C-u Z perhaps?

  reply	other threads:[~2019-11-12 14:01 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 [this message]
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

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=87woc5urbv.fsf@jb55.com \
    --to=jb55@jb55.com \
    --cc=dme@dme.org \
    --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).