unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mark Walters <markwalters1009@gmail.com>
To: Daniel Schoepe <daniel@schoepe.org>,
	Jameson Graef Rollins <jrollins@finestructure.net>,
	notmuch@notmuchmail.org
Subject: Re: RFC notmuch-pick: an emacs threaded message view with split-pane
Date: Sun, 12 Feb 2012 21:43:42 +0000	[thread overview]
Message-ID: <8739afsp69.fsf@qmul.ac.uk> (raw)
In-Reply-To: <877gzru5s4.fsf@schoepe.localhost>


On Sun, 12 Feb 2012 21:59:39 +0100, Daniel Schoepe <daniel@schoepe.org> wrote:
> On Sun, 12 Feb 2012 12:46:36 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> > Hey, Mark.  I really like the idea, since I've been looking for
> > something like this for a while, but there's something I'm confused
> > about.  Is this meant to replace notmuch-search, or notmuch-show?  I had
> > been hoping for a notmuch *show* replacement that shows the nice tree
> > view for the thread, with a single message view below.  But it sounds
> > like you're meant to be replacing notmuch search?  That seems confusing
> > to me, particularly in light of the big performance hit you describe.
> 
> As far as I can tell, it is intended as a third option and can be used
> for both, viewing all messages matching a search in a tree structure
> (with a pane for an individual message) as in most other mail clients
> (mutt, thunderbird, Gnus, etc.) and viewing a single thread in the
> manner you described.
> 
> This has the added bonus, that it can be offered _in addition_ to show
> in search, since I wouldn't want to give up the current
> search-view. notmuch-show might also be preferred by some users (due to
> its similarity to sup and gmail). Of course, this would mean that we
> would have to maintain threading capabilities for two modes. (It relies
> on show for displaying a single message, so that part is not
> duplicated).

This is exactly my view: it comes somewhere between search and show. I
use it both ways: as a view for my inbox (i.e., as a replacement for
search) and when I get lost "showing" a long thread. 

I haven't tried Daniel's suggestion of notmuch-search-pick (going from a
thread to the pick view of that thread). But I will add it as an option.

Best wishes

Mark

      reply	other threads:[~2012-02-12 21:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 10:32 RFC notmuch-pick: an emacs threaded message view with split-pane Mark Walters
2012-02-12 10:36 ` [RFC PATCH 1/3] cli: notmuch-show changes to support pick Mark Walters
2012-02-12 10:36 ` [RFC PATCH 2/3] emacs: changes to other files to support notmuch-pick Mark Walters
2012-02-12 10:36 ` [RFC PATCH 3/3] emacs: add notmuch-pick itself Mark Walters
     [not found] ` <87ehu0cf16.fsf@schoepe.localhost>
2012-02-12 14:31   ` RFC notmuch-pick: an emacs threaded message view with split-pane Daniel Schoepe
2012-02-12 14:47 ` [PATCH 0/1] emacs: Make highlight-faces for pick configurable Daniel Schoepe
2012-02-12 14:47   ` [PATCH] " Daniel Schoepe
2012-02-12 15:50     ` Mark Walters
2012-02-12 20:46 ` RFC notmuch-pick: an emacs threaded message view with split-pane Jameson Graef Rollins
2012-02-12 20:59   ` Daniel Schoepe
2012-02-12 21:43     ` Mark Walters [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=8739afsp69.fsf@qmul.ac.uk \
    --to=markwalters1009@gmail.com \
    --cc=daniel@schoepe.org \
    --cc=jrollins@finestructure.net \
    --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).