1 Return-Path: <racin@free.fr>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 6C1CF431FD0
\r
6 for <notmuch@notmuchmail.org>; Mon, 4 Jul 2011 14:36:47 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
\r
12 tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001]
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id iTINf-8GeFTW for <notmuch@notmuchmail.org>;
\r
17 Mon, 4 Jul 2011 14:36:46 -0700 (PDT)
\r
18 Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [212.27.42.3])
\r
19 by olra.theworths.org (Postfix) with ESMTP id BC669431FB6
\r
20 for <notmuch@notmuchmail.org>; Mon, 4 Jul 2011 14:36:45 -0700 (PDT)
\r
21 Received: from matthieu-netbook (unknown [82.239.207.166])
\r
22 by smtp3-g21.free.fr (Postfix) with ESMTP id E7864A60E4;
\r
23 Mon, 4 Jul 2011 23:36:36 +0200 (CEST)
\r
24 From: Matthieu Lemerre <racin@free.fr>
\r
25 To: Robin Green <greenrd@greenrd.org>, Notmuch Mail <notmuch@notmuchmail.org>
\r
26 Subject: Dangerous space bar key (was: Preventing the user shooting themself
\r
28 In-Reply-To: <86iproe86u.fsf@greenrd.plus.com>
\r
29 References: <86iproe86u.fsf@greenrd.plus.com>
\r
30 User-Agent: Notmuch/0.6+mwhudson+1700~natty1 (http://notmuchmail.org)
\r
31 Emacs/23.2.1 (i686-pc-linux-gnu)
\r
32 Date: Mon, 04 Jul 2011 23:36:35 +0200
\r
33 Message-ID: <877h7xafto.fsf@free.fr>
\r
35 Content-Type: text/plain; charset=us-ascii
\r
36 X-BeenThere: notmuch@notmuchmail.org
\r
37 X-Mailman-Version: 2.1.13
\r
39 List-Id: "Use and development of the notmuch mail system."
\r
40 <notmuch.notmuchmail.org>
\r
41 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
42 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
43 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
44 List-Post: <mailto:notmuch@notmuchmail.org>
\r
45 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
46 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
47 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
48 X-List-Received-Date: Mon, 04 Jul 2011 21:36:47 -0000
\r
50 On Wed, 29 Jun 2011 20:42:01 +0100, Robin Green <greenrd@greenrd.org> wrote:
\r
51 > It's really dangerous to use the 'a' key in notmuch-mode in an inbox
\r
52 > thread which has multiple unread replies! Yes, the other unread replies
\r
53 > will still be tagged unread, but the user might not immediately be aware
\r
54 > of them. It would be really useful to have an optional warning ("More
\r
55 > unread messages in this thread, are you sure?") for this situation!
\r
57 I take advantage of this thread to tell about another dangerous
\r
58 situation I've found related to the use of the space key in show mode.
\r
60 I like to use the space (and sometimes the backspace key) to read
\r
61 threads back and forth, but sometimes I might read stuff to quickly and
\r
62 archive a thread without wanting it. It is then complex to find it back
\r
63 (especially if the thread contained a single message and I hit space
\r
64 before actually reading the message, so I can't find it again).
\r
66 As a workaround, I have changed the space key function
\r
67 "notmuch-show-advance-and-archive" to not archive the thread if we are
\r
68 at the end of the thread, but to just do nothing. Thus I have to
\r
69 expicitely archive the thread when I have finished reading it, which I
\r
72 I think the "and-archive" part of the space bar key should be at least
\r
73 configurable. The patch is pretty simple but I can provide it if needed.
\r
75 Note: The n and p keys are not good replacement for space/backspace.
\r
76 First, because they do not remove the 'read' tag. Second, when you are
\r
77 in the middle of a message, the p key go to the previous message instead
\r
78 of going on top of the current one. (Actually, the behaviour of n is
\r
79 fine, only p is annoying me). I think this is inconsistent with what
\r
80 others mode do (e.g. C-M-u in programming modes, or C-c C-p in
\r
81 org-mode), and the p key when in a message should go to the beginning of
\r
82 the current message.
\r