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 07:48:25 +0200 [thread overview]
Message-ID: <87sfx83ydy.fsf@gmail.com> (raw)
In-Reply-To: <83k0ikqp1x.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Oct 2021 05:21:30 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sun, 10 Oct 2021 21:07:16 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: emacs-devel@gnu.org
>>
>> If you don't want to use 4 or 5 for both, let's find a different
>> letter, but make it identical for both "C-x 4" and "C-x 5".
>
> How about "C-x 4 x" and "C-x 5 x". where "x" stands for "eXecute"?
> An alternative could be "C-x 4 RET" and "C-x 5 RET".
>
> Would any of these be acceptable?
I don't mind x or RET in terms of mnemonics, but my clumsy fingers find
them less ergonomic than C-x K K.
FWIW, I don't find it shocking that other-{frame,tab,window}-prefix do
not end with identical letters. True, they are the only commands in the
{ctl-x-4,ctl-x-5,tab-prefix}-map keymaps that break this convention, but
they still follow a consistent pattern: C-x K K, where K is the prefix
key for the relevant UI element.
I also support Juri's suggestion to bind tear-off-window to C-x 4 5: I
feel like the "_4_ to _5_" sequence translates quite well to "move this
_window_ to another _frame_", at least in my head.
next prev parent reply other threads:[~2021-10-11 5:48 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 [this message]
2021-10-11 12:11 ` Eli Zaretskii
2021-10-11 13:18 ` Kévin Le Gouguec
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=87sfx83ydy.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).