unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: Carl Worth <cworth@cworth.org>, Robin Green <greenrd@greenrd.org>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Preventing the user shooting themself in the foot
Date: Thu, 30 Jun 2011 08:29:09 +0200	[thread overview]
Message-ID: <877h83rfwq.fsf@SSpaeth.de> (raw)
In-Reply-To: <87fwms45xz.fsf@yoom.home.cworth.org>

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

On Wed, 29 Jun 2011 15:40:40 -0700, Carl Worth <cworth@cworth.org> wrote:
> On Wed, 29 Jun 2011 20:42:01 +0100, Robin Green <greenrd@greenrd.org> wrote:
> > It's really dangerous to use the 'a' key in notmuch-mode in an inbox
> > thread which has multiple unread replies! Yes, the other unread replies
> > will still be tagged unread, but the user might not immediately be aware
> > of them. It would be really useful to have an optional warning ("More
> > unread messages in this thread, are you sure?") for this situation!
> 
> That was why I originally designed the space bar keybinding for reading
> through each message in turn, (and then it archives the thread only when you
> page past the last message).
> 
> The 'a' keybinding, (in turn), was designed for cases when you *know*
> you don't want to read the rest of the thread.

And that is what I use 'a' for, please don't take the single-key binding
away for this. I often glance at a thread, decide it's not interesting
for me and archive the whole thread including all unread messages.

It works perfectly for me. Adding another key for "only archive this
message" would be fine. Do people actually use the "x" keybinding? I
know I don't.

Sebastian

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

  parent reply	other threads:[~2011-06-30  6:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 19:42 Preventing the user shooting themself in the foot Robin Green
2011-06-29 20:37 ` Jameson Graef Rollins
2011-06-29 22:40 ` Carl Worth
2011-06-30  3:04   ` Brian May
2011-06-30  4:10     ` Jameson Graef Rollins
2011-06-30  5:40     ` Carl Worth
2011-06-30  7:45       ` Pieter Praet
2011-06-30 21:26       ` Michael Hudson-Doyle
2011-07-01 16:37         ` Jameson Graef Rollins
2011-07-01 17:17           ` Austin Clements
2011-07-01 17:11         ` Pieter Praet
2011-06-30 23:02       ` Stewart Smith
2011-06-30  6:29   ` Sebastian Spaeth [this message]
2011-07-04 20:09     ` Michal Sojka
2011-07-04 21:36 ` Dangerous space bar key (was: Preventing the user shooting themself in the foot) Matthieu Lemerre
2011-07-05  0:03   ` Jameson Graef Rollins
2011-07-05 20:23     ` Matthieu Lemerre
2011-07-06 13:25       ` Austin Clements
2011-07-07 18:49         ` Matthieu Lemerre
2011-07-07 20:40           ` Jameson Graef Rollins
2011-07-07 20:58             ` Austin Clements
2011-07-07 21:17               ` Jameson Graef Rollins
2011-07-09 17:09 ` Preventing the user shooting themself in the foot Neeum Zawan
2011-07-09 20:32   ` Daniel Schoepe
  -- strict thread matches above, loose matches on Subject: below --
2011-06-29 23:53 Austin Clements
2011-06-30  7:50 ` Pieter Praet
2011-06-30  8:51   ` Pieter Praet
2011-07-01  1:28   ` Brian May
2011-07-01 21:44     ` Pieter Praet

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=877h83rfwq.fsf@SSpaeth.de \
    --to=sebastian@sspaeth.de \
    --cc=cworth@cworth.org \
    --cc=greenrd@greenrd.org \
    --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).