From: Drew Adams <drew.adams@oracle.com>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
"dgutov@yandex.ru" <dgutov@yandex.ru>
Subject: RE: [External] : Adding a binding for 'undo-redo'
Date: Wed, 29 Sep 2021 17:25:04 +0000 [thread overview]
Message-ID: <SJ0PR10MB54883068E48A9BE43A7BEE93F3A99@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <E1mVd4f-0005rb-3G@fencepost.gnu.org>
> The "technical hurdle" of finding a good binding
> isn't the place to start. The place to start is
> to wait for users to use and bind it, and then
> see how much a default binding would make sense.
>
> Here lies chaos.
>
> For coherent design, and logical keybindings, one cannot wait until
> users have bound a key. It is a good indication of what might be
> used, but not what might make sense in the grand picture.
There may not be a reason to always wait - agreed.
("One cannot wait" ever is clearly wrong, though.)
It doesn't follow that every command should get a
default key binding. And how new the redo command
is isn't really the question, on its own.
The question really should be how useful the command
is, in practice: How much are users using it, and how
important would it be for it to have a default binding?
next prev parent reply other threads:[~2021-09-29 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 1:56 Adding a binding for 'undo-redo' Dmitry Gutov
2021-09-29 5:38 ` Lars Ingebrigtsen
2021-09-29 11:26 ` Dmitry Gutov
2021-09-29 12:21 ` Bozhidar Batsov
2021-09-29 15:50 ` Lars Ingebrigtsen
2021-09-29 19:37 ` Dmitry Gutov
2021-09-29 16:26 ` [External] : " Drew Adams
2021-09-29 13:02 ` Eli Zaretskii
2021-09-29 16:25 ` [External] : " Drew Adams
2021-09-29 16:34 ` Eli Zaretskii
2021-09-29 16:46 ` Manuel Uberti
2021-09-29 17:08 ` Alfred M. Szmidt
2021-09-29 17:25 ` Drew Adams [this message]
2021-09-29 19:17 ` Dmitry Gutov
2021-09-29 19:29 ` Drew Adams
2021-09-30 7:13 ` Alfred M. Szmidt
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB54883068E48A9BE43A7BEE93F3A99@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=ams@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).