1 Return-Path: <jrollins@finestructure.net>
\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 02512431FD0
\r
6 for <notmuch@notmuchmail.org>; Thu, 7 Jul 2011 14:17:26 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id F4ncyUTKdtPF for <notmuch@notmuchmail.org>;
\r
16 Thu, 7 Jul 2011 14:17:25 -0700 (PDT)
\r
17 Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu
\r
19 by olra.theworths.org (Postfix) with ESMTP id 5965E431FB6
\r
20 for <notmuch@notmuchmail.org>; Thu, 7 Jul 2011 14:17:25 -0700 (PDT)
\r
21 Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])
\r
22 by fire-doxen-postvirus (Postfix) with ESMTP id DC8BD2E50E32;
\r
23 Thu, 7 Jul 2011 14:08:01 -0700 (PDT)
\r
24 X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new
\r
25 Received: from servo.finestructure.net (gwave-180.ligo.caltech.edu
\r
26 [131.215.114.180]) (Authenticated sender: jrollins)
\r
27 by fire-doxen-submit (Postfix) with ESMTP id CE5172E50DBE;
\r
28 Thu, 7 Jul 2011 14:07:56 -0700 (PDT)
\r
29 Received: by servo.finestructure.net (Postfix, from userid 1000)
\r
30 id 7FEFB291; Thu, 7 Jul 2011 14:17:17 -0700 (PDT)
\r
31 From: Jameson Graef Rollins <jrollins@finestructure.net>
\r
32 To: Austin Clements <amdragon@MIT.EDU>
\r
33 Subject: Re: Dangerous space bar key (was: Preventing the user shooting
\r
34 themself in the foot)
\r
35 In-Reply-To: <20110707205808.GF18563@mit.edu>
\r
36 References: <86iproe86u.fsf@greenrd.plus.com> <877h7xafto.fsf@free.fr>
\r
37 <87pqlpioew.fsf@servo.factory.finestructure.net>
\r
38 <87wrfwpjdi.fsf@free.fr>
\r
39 <CAH-f9Ws6Ji_H3JnkJS1jtio8_-65C_J5iAOnn6XsGp7YSuX2eA@mail.gmail.com>
\r
40 <87mxgqgc3k.fsf@free.fr>
\r
41 <87d3hlg6ye.fsf@servo.factory.finestructure.net>
\r
42 <20110707205808.GF18563@mit.edu>
\r
43 User-Agent: Notmuch/0.5-292-gaa2fa19 (http://notmuchmail.org) Emacs/23.3.1
\r
44 (x86_64-pc-linux-gnu)
\r
45 Date: Thu, 07 Jul 2011 14:17:17 -0700
\r
46 Message-ID: <878vs9g59e.fsf@servo.factory.finestructure.net>
\r
48 Content-Type: multipart/signed; boundary="=-=-=";
\r
49 micalg=pgp-sha256; protocol="application/pgp-signature"
\r
50 Cc: Notmuch Mail <notmuch@notmuchmail.org>
\r
51 X-BeenThere: notmuch@notmuchmail.org
\r
52 X-Mailman-Version: 2.1.13
\r
54 List-Id: "Use and development of the notmuch mail system."
\r
55 <notmuch.notmuchmail.org>
\r
56 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
57 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
58 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
59 List-Post: <mailto:notmuch@notmuchmail.org>
\r
60 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
61 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
62 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
63 X-List-Received-Date: Thu, 07 Jul 2011 21:17:26 -0000
\r
67 On Thu, 7 Jul 2011 16:58:08 -0400, Austin Clements <amdragon@MIT.EDU> wrote:
\r
68 > What I'm suggesting is no more or less automatic than the current
\r
69 > behavior. It's just a slight tweak to the order in which things
\r
70 > happen: that SPC could remove the unread tag and then move to the next
\r
71 > message, rather than the other way around. In effect, the read tag
\r
72 > would indicate that you've seen the bottom of the message, not just
\r
75 But as it stands now, the unread tag automatically goes away as soon as
\r
76 view the message when selected from notmuch-search. Under the new
\r
77 proposal I would have to hit SPC to remove the unread tag, even if the
\r
78 whole message was already visible. It would still require more work.
\r
80 > It's also possible I would have less trouble if SPC didn't
\r
81 > automatically go to the next thread. The problem I have with the
\r
82 > current behavior is that I often find myself accidentally marking
\r
83 > messages as read because notmuch showed me a message I wasn't
\r
84 > expecting. This is compounded by the lack of visual feedback when
\r
85 > this happens (e.g., the search results don't update to indicate that
\r
86 > anything has changed, and even if they did, I probably wouldn't notice
\r
87 > that the message *had* been unread).
\r
89 I really think the problem is the current behavior of SPC. As I and a
\r
90 couple of others have already mentioned, it just not a good, intuitive
\r
91 default behavior. I suggested what I think is a much better behavior in
\r
92 a previous message [0].
\r
96 [0] id:"87pqlpioew.fsf@servo.factory.finestructure.net"
\r
99 Content-Type: application/pgp-signature
\r
101 -----BEGIN PGP SIGNATURE-----
\r
102 Version: GnuPG v1.4.11 (GNU/Linux)
\r
104 iQIcBAEBCAAGBQJOFiJdAAoJEO00zqvie6q8A5sQAK0hV18+rW95Qc54Pa5I6WIP
\r
105 C2YAbrAa2fLv9V6XhgjR2I6lK1UdA532QYoShwJjVzC0qiFfUusVsCzqTilIijJ5
\r
106 a0aj1wxL2BHYwOysJQ0glUBNFzlNQ4anmSiuf/gFEqAcSDGskfktF7zfzcGNP7Rv
\r
107 C8ysJ8nNUi77YXKbNkZk0ilRJXEVw7mb2cRKrETJ5eUkhCTcme6cbpzBau+2S9xT
\r
108 REvHam8hw2uhtEzBsHnfeh3dDLFyPt3KPMy1r0BHa9+TnywpkpQ9PZHhvERehbev
\r
109 py1PF0mcwdyGLXf5pMwV+gMtyAqGEIxs8oU+Z+R8Ul0qz+oH1YV5q78e4wspXwHT
\r
110 KBqBdIAb4Gy2/tiQ0vVu+KIX2gvOTuws1mEtZk2ZjEAl9hxKs2/Sbncmhzbe6SgZ
\r
111 M3OlsGKG1NNXsXTjO4vHtesr0FMk1LSiEJjdGZHZJbVPS+iIyw15ZlVKJfUwhRpC
\r
112 QE3ERhNdj8YL6o5ZH4ZM0JDR1I1XVRMDM2I6LUa30hRbg0qLQ6OK+/Je4k1NMDQD
\r
113 QPYHbsann+u/6/tVeGgPbaEtEA3XsV/UDDbsqQGxeM7NxDOyE2CZ78CuMn0N+WuN
\r
114 RmOHyZ5Ppn6pss75kwx5axbzB0FoXxT1/MIEOLj/tEjRi79szMx6iJ3PiA05JtUj
\r
115 Tb9SeGdDa9FU8JNILwZ9
\r
117 -----END PGP SIGNATURE-----
\r