From: Austin Clements <amdragon@mit.edu>
To: Carl Worth <cworth@cworth.org>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Preventing the user shooting themself in the foot
Date: Wed, 29 Jun 2011 19:53:03 -0400 [thread overview]
Message-ID: <CAH-f9Ws8oNb_UzzPNGsw0V29Rh0VTK2Tz0voG0QwLPcKTq1fCw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
I've spent embarrassingly little time in the emacs UI, so my opinions on
this should be taken lightly, but I feel like all of the bindings are of the
form "if W, do X and Y, otherwise do Z" and, as a result, I'm actively
afraid of what's going to happen when I hit a key. I would much prefer
bindings with simple, highly predictable behavior. I'm sure there's some
workflow for which these contextual, compound bindings are fantastic, but
other workflows wind up fighting against them.
I don't have a specific proposal in mind, but Gmail's bindings seem like a
good model to emulate (the actions, at least; I've never been too fond of
the specific key choices).
On Jun 29, 2011 6:40 PM, "Carl Worth" <cworth@cworth.org> wrote:
[-- Attachment #2: Type: text/html, Size: 897 bytes --]
next reply other threads:[~2011-06-29 23:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 23:53 Austin Clements [this message]
2011-06-30 7:50 ` Preventing the user shooting themself in the foot Pieter Praet
2011-06-30 8:51 ` Pieter Praet
2011-07-01 1:28 ` Brian May
2011-07-01 21:44 ` Pieter Praet
-- strict thread matches above, loose matches on Subject: below --
2011-06-29 19:42 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-09 17:09 ` 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=CAH-f9Ws8oNb_UzzPNGsw0V29Rh0VTK2Tz0voG0QwLPcKTq1fCw@mail.gmail.com \
--to=amdragon@mit.edu \
--cc=cworth@cworth.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).