From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Austin Clements <amdragon@MIT.EDU>
Subject: Re: Dangerous space bar key (was: Preventing the user shooting
	themself in the foot)
In-Reply-To: <20110707205808.GF18563@mit.edu>
References: <86iproe86u.fsf@greenrd.plus.com> <877h7xafto.fsf@free.fr>
	<87pqlpioew.fsf@servo.factory.finestructure.net>
	<87wrfwpjdi.fsf@free.fr>
	<CAH-f9Ws6Ji_H3JnkJS1jtio8_-65C_J5iAOnn6XsGp7YSuX2eA@mail.gmail.com>
	<87mxgqgc3k.fsf@free.fr>
	<87d3hlg6ye.fsf@servo.factory.finestructure.net>
	<20110707205808.GF18563@mit.edu>
User-Agent: Notmuch/0.5-292-gaa2fa19 (http://notmuchmail.org) Emacs/23.3.1
	(x86_64-pc-linux-gnu)
Date: Thu, 07 Jul 2011 14:17:17 -0700
Message-ID: <878vs9g59e.fsf@servo.factory.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Precedence: list

--=-=-=

On Thu, 7 Jul 2011 16:58:08 -0400, Austin Clements <amdragon@MIT.EDU> wrote:
> What I'm suggesting is no more or less automatic than the current
> behavior.  It's just a slight tweak to the order in which things
> happen: that SPC could remove the unread tag and then move to the next
> message, rather than the other way around.  In effect, the read tag
> would indicate that you've seen the bottom of the message, not just
> the top.

But as it stands now, the unread tag automatically goes away as soon as
view the message when selected from notmuch-search.  Under the new
proposal I would have to hit SPC to remove the unread tag, even if the
whole message was already visible.  It would still require more work.

> It's also possible I would have less trouble if SPC didn't
> automatically go to the next thread.  The problem I have with the
> current behavior is that I often find myself accidentally marking
> messages as read because notmuch showed me a message I wasn't
> expecting.  This is compounded by the lack of visual feedback when
> this happens (e.g., the search results don't update to indicate that
> anything has changed, and even if they did, I probably wouldn't notice
> that the message *had* been unread).

I really think the problem is the current behavior of SPC.  As I and a
couple of others have already mentioned, it just not a good, intuitive
default behavior.  I suggested what I think is a much better behavior in
a previous message [0].

jamie.

[0] id:"87pqlpioew.fsf@servo.factory.finestructure.net"

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJOFiJdAAoJEO00zqvie6q8A5sQAK0hV18+rW95Qc54Pa5I6WIP
C2YAbrAa2fLv9V6XhgjR2I6lK1UdA532QYoShwJjVzC0qiFfUusVsCzqTilIijJ5
a0aj1wxL2BHYwOysJQ0glUBNFzlNQ4anmSiuf/gFEqAcSDGskfktF7zfzcGNP7Rv
C8ysJ8nNUi77YXKbNkZk0ilRJXEVw7mb2cRKrETJ5eUkhCTcme6cbpzBau+2S9xT
REvHam8hw2uhtEzBsHnfeh3dDLFyPt3KPMy1r0BHa9+TnywpkpQ9PZHhvERehbev
py1PF0mcwdyGLXf5pMwV+gMtyAqGEIxs8oU+Z+R8Ul0qz+oH1YV5q78e4wspXwHT
KBqBdIAb4Gy2/tiQ0vVu+KIX2gvOTuws1mEtZk2ZjEAl9hxKs2/Sbncmhzbe6SgZ
M3OlsGKG1NNXsXTjO4vHtesr0FMk1LSiEJjdGZHZJbVPS+iIyw15ZlVKJfUwhRpC
QE3ERhNdj8YL6o5ZH4ZM0JDR1I1XVRMDM2I6LUa30hRbg0qLQ6OK+/Je4k1NMDQD
QPYHbsann+u/6/tVeGgPbaEtEA3XsV/UDDbsqQGxeM7NxDOyE2CZ78CuMn0N+WuN
RmOHyZ5Ppn6pss75kwx5axbzB0FoXxT1/MIEOLj/tEjRi79szMx6iJ3PiA05JtUj
Tb9SeGdDa9FU8JNILwZ9
=sdLC
-----END PGP SIGNATURE-----
--=-=-=--