From: Dirk Hohndel <hohndel@infradead.org>
To: Carl Worth <cworth@cworth.org>,
Jameson Rollins <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: The archive operation should only archive open messages
Date: Sat, 17 Apr 2010 11:14:51 -0700 [thread overview]
Message-ID: <m3zl1254kk.fsf@x200.gr8dns.org> (raw)
In-Reply-To: <87r5me2j4e.fsf@yoom.home.cworth.org>
On Sat, 17 Apr 2010 08:28:49 -0700, Carl Worth <cworth@cworth.org> wrote:
> On Thu, 15 Apr 2010 16:59:13 -0400, Jameson Rollins <jrollins@finestructure.net> wrote:
> > I actually *really* don't like that the space bar does this. In fact, I
> > build my own notmuch-show-advance function in a notmuch-hacks.el that I
> > load to expressly get around this.
>
> Well we definitely do need that operation ("advance to next thread
> without archiving" to complement our existing "advance to next thread
> after archiving"). Any suggestions for what the keybinding should be for
> that? What are you using?
I have been going back and forth about which key to use... My current
favorite is 'k'eep. It kind of mirrors nicely with 'a'rchive.
> And once we have that, changing space bar to only operate within the
> current thread and not doing any advancing will definitely make it a lot
> less magic and less confusing.
Yes, please.
/D
--
Dirk Hohndel
Intel Open Source Technology Center
next prev parent reply other threads:[~2010-04-17 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 20:41 The archive operation should only archive open messages Carl Worth
2010-04-15 20:59 ` Jameson Rollins
2010-04-17 15:28 ` Carl Worth
2010-04-17 18:14 ` Dirk Hohndel [this message]
2010-04-15 21:07 ` Dirk Hohndel
2010-04-16 1:51 ` Carl Worth
2010-04-15 21:18 ` Jesse Rosenthal
2010-04-17 15:36 ` Carl Worth
2010-04-20 7:37 ` racin
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=m3zl1254kk.fsf@x200.gr8dns.org \
--to=hohndel@infradead.org \
--cc=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).