Re: Dangerous space bar key (was: Preventing the user shooting themself in the foot)

[Matthieu Lemerre <racin@free.fr>]

On Mon, 04 Jul 2011 17:03:51 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/signed
> On Mon, 04 Jul 2011 23:36:35 +0200, Matthieu Lemerre <racin@free.fr> wrote:
> > 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 completely agree with your discomfort with the current function bound
> to space.  I don't like it at all, and I similarly rebound space to be a
> much more sensible function:

[...]

> Notice I also made it so that this does not exit the current thread
> view.

I patched notmuch to use exactly the same function... Given that we are
two people who independently requested for this behaviour, I think this
should at least be a customisable option, and imo the default should do
nothing and not archive the thread because of this dangerous
behaviour. And, hitting 'a' instead of space to go to the next thread is
the same number of keypresses...

Matthieu