unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: "C-x 5 5" vs "C-x 4 1" inconsistency
Date: Sun, 10 Oct 2021 11:03:31 +0200	[thread overview]
Message-ID: <87sfx9i74s.fsf@gmail.com> (raw)
In-Reply-To: <8735p9jo51.fsf@mail.linkov.net> (Juri Linkov's message of "Sun,  10 Oct 2021 11:10:50 +0300")

Juri Linkov <juri@linkov.net> writes:

>>> I think this inconsistency is unfortunate and unjustified.  Can we
>>> please move same-window-prefix to "C-x 4 5" for consistency with the
>>> equivalent frame command?
>>
>> Sorry, I meant "C-x 4 4" and other-window-prefix.
>
> Please explain where do you think is inconsistency.
> 'C-x 4 4' is already bound to 'other-window-prefix'.

IIUC Eli would find C-x 4 5 more consistent for other-window-prefix (I
hope I ran the substitutions correctly; apologies if not).

Personally I like the current arrangement: I think of it as "C-x X X for
other-Y-prefix", with

- X=4 ⇒ Y=window
- X=5 ⇒ Y=frame
- X=t ⇒ Y=tab

I find "mash X to run in new Y" simpler to remember than "press X then 5
to run in new Y".



  reply	other threads:[~2021-10-10  9:03 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 [this message]
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

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=87sfx9i74s.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).