unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Jameson Rollins <jrollins@finestructure.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] remove message archiving from show-advance-and-archive
Date: Wed, 09 Jun 2010 10:50:15 -0700	[thread overview]
Message-ID: <871vcghz8o.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87zkz4xnf4.fsf@servo.finestructure.net>

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

On Wed, 9 Jun 2010 10:49:43 -0400, Jameson Rollins <jrollins@finestructure.net> wrote:
> The function to advance through threads with the space bar is useful.
> However, the current implementation also archives messages.  The idea
> of archiving a message should not be intertwined with the processes of
> advancing through messages to read them.  Archiving in general should
> be a separate operation that one does explicitly.  This patch just
> renames the advance function "notmuch-show-advance", and removes the
> archiving of a thread when the end of the thread is reached.

The other piece of the magic space bar that people have complained about
is that it intertwines advancing among messages within one thread with
advancing from one thread to the next. (And only the first operation is
reversible by backspace.)

I think we'll probably want to change that at the same time.

Meanwhile, I'm currently working on support for piping a whole thread of
messages as an mbox to a process, (mostly getting bogged down in trying
to fix mbox support in git).

For that, I think I want the current '|' binding to pipe the current
message and then a new binding ("M-|" ?) to pipe every (open) message in
the thread.

Which makes me think that other operations should work similarly. '+'
and '-' should change tags on the current message (as they do currently)
and then new "M-+" and "M--" could change tags on all (open) messages in
the thread.

That would highlight the current 'a' as out of place since it's
currently archiving every message in the thread. So I'd then fix it to
be 'a' for the current message and "M-a" for every (open) message in the
thread.

What do people think of that?

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2010-06-09 17:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 14:49 [PATCH] remove message archiving from show-advance-and-archive Jameson Rollins
2010-06-09 15:12 ` David Edmondson
2010-06-09 15:25   ` Jameson Rollins
2010-06-09 15:36     ` David Edmondson
2010-06-09 15:55       ` Jameson Rollins
2010-06-09 17:18         ` David Edmondson
2010-06-09 17:29           ` Jameson Rollins
2010-06-09 17:47             ` David Edmondson
2010-06-09 17:54         ` Carl Worth
2010-06-09 19:07           ` servilio
2010-06-09 19:11           ` Jameson Rollins
2010-06-09 17:50 ` Carl Worth [this message]
2010-06-09 18:20   ` Dirk Hohndel
2010-06-09 19:12     ` servilio
2010-06-09 19:20     ` Jameson Rollins
2010-06-09 19:33       ` Carl Worth
2010-06-15  9:25     ` Sebastian Spaeth
2010-06-09 19:04   ` servilio
2010-06-09 19:18   ` Jameson Rollins
2010-06-09 19:55   ` Michal Sojka
2010-06-15  9:21   ` Sebastian Spaeth

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=871vcghz8o.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.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).