From: Matthieu Lemerre <racin@free.fr>
To: Robin Green <greenrd@greenrd.org>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Dangerous space bar key (was: Preventing the user shooting themself in the foot)
Date: Mon, 04 Jul 2011 23:36:35 +0200 [thread overview]
Message-ID: <877h7xafto.fsf@free.fr> (raw)
In-Reply-To: <86iproe86u.fsf@greenrd.plus.com>
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!
I take advantage of this thread to tell about another dangerous
situation I've found related to the use of the space key in show mode.
I like to use the space (and sometimes the backspace key) to read
threads back and forth, but sometimes I might read stuff to quickly and
archive a thread without wanting it. It is then complex to find it back
(especially if the thread contained a single message and I hit space
before actually reading the message, so I can't find it again).
As a workaround, I have changed the space key function
"notmuch-show-advance-and-archive" to not archive the thread if we are
at the end of the thread, but to just do nothing. Thus I have to
expicitely archive the thread when I have finished reading it, which I
find much safer.
I think the "and-archive" part of the space bar key should be at least
configurable. The patch is pretty simple but I can provide it if needed.
Note: The n and p keys are not good replacement for space/backspace.
First, because they do not remove the 'read' tag. Second, when you are
in the middle of a message, the p key go to the previous message instead
of going on top of the current one. (Actually, the behaviour of n is
fine, only p is annoying me). I think this is inconsistent with what
others mode do (e.g. C-M-u in programming modes, or C-c C-p in
org-mode), and the p key when in a message should go to the beginning of
the current message.
Matthieu
next prev parent reply other threads:[~2011-07-04 21:36 UTC|newest]
Thread overview: 24+ 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
2011-07-04 20:09 ` Michal Sojka
2011-07-04 21:36 ` Matthieu Lemerre [this message]
2011-07-05 0:03 ` Dangerous space bar key (was: Preventing the user shooting themself in the foot) 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
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=877h7xafto.fsf@free.fr \
--to=racin@free.fr \
--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).