unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, juri@linkov.net
Subject: Re: "C-x 5 5" vs "C-x 4 1" inconsistency
Date: Mon, 11 Oct 2021 15:18:53 +0200	[thread overview]
Message-ID: <87lf2zn1he.fsf@gmail.com> (raw)
In-Reply-To: <83ee8rrcat.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Oct 2021 15:11:38 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> That's a peculiar argument.  There's only one "C-x K K" combination
> for any K, and yet we have more than a dozen commands starting with
> "C-x 4" and similarly for "C-x 5".  Does it mean that all but one of
> them is not ergonomic?

All I meant was that given a choice between C-x K K and C-x K x, the
former feels more "ergonomic" (by which I mostly mean "durr mashing same
key twice is easy, me likes it 🤪"; dunno if Stefan's definition of the
word is more sophisticated[1]).

I did not mean to comment on the dozen other commands in
{ctl-x-4,ctl-x-5,tab-prefix}-map (I don't find C-x [45] very ergonomic
anyway on AZERTY, since digits require holding Shift).

I acknowledge that the ergonomics argument, by itself, does not justify
breaking the current convention ("similar commands end with identical
keys"), and there is no reason a priori that C-x K K, "ergonomic" as it
might be, should be given to other-X-prefix.

All I can say is that it makes some intuitive sense to me: commands
starting with C-x K ∀K∈{4,5,t} generally mean "Do/find/visit something
in another X", therefore "hit K twice to run next command in another X"
does not sound too outlandish.


[1] <CADwFkmnoMJeUGfPS5jAbYso0fWCLOrYnWuW7FcFvnZx0mpuqYg@mail.gmail.com>
    https://lists.gnu.org/archive/html/emacs-devel/2021-10/msg00765.html



      reply	other threads:[~2021-10-11 13:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09  9:26 "C-x 5 5" vs "C-x 4 1" inconsistency Eli Zaretskii
2021-10-09  9:30 ` Eli Zaretskii
2021-10-10  8:10   ` Juri Linkov
2021-10-10  9:03     ` Kévin Le Gouguec
2021-10-10  9:16       ` Stefan Kangas
2021-10-10 10:41     ` Eli Zaretskii
2021-10-10 13:28       ` Daniel Martín
2021-10-10 17:15       ` Juri Linkov
2021-10-10 18:07         ` Eli Zaretskii
2021-10-10 19:02           ` Juri Linkov
2021-10-10 19:21             ` Eli Zaretskii
2021-10-11  6:13               ` Juri Linkov
2021-10-10 23:32           ` Stefan Kangas
2021-10-11  2:21           ` Eli Zaretskii
2021-10-11  5:48             ` Kévin Le Gouguec
2021-10-11 12:11               ` Eli Zaretskii
2021-10-11 13:18                 ` Kévin Le Gouguec [this message]

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=87lf2zn1he.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).