unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: "C-x 5 5" vs "C-x 4 1" inconsistency
Date: Sun, 10 Oct 2021 16:32:47 -0700	[thread overview]
Message-ID: <CADwFkmnoMJeUGfPS5jAbYso0fWCLOrYnWuW7FcFvnZx0mpuqYg@mail.gmail.com> (raw)
In-Reply-To: <83r1csrbxn.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> The prefix 'C-x 5' is for frames, so 'C-x 5 5' creates a new frame.
>> The prefix 'C-x 4' is for windows, so 'C-x 4 4' creates a new window.
>> Also like 'C-x 1' keeps the selected window, 'C-x 4 1' shows the next
>> buffer in the same window while keeping it selected.
>
> And what do you say about the other examples I gave above?
>
> It was always the rule with these commands that similar operations
> have the same "final" keys.  Now you've broken this.  I think this is
> not a good situation.  It will definitely get in the way of my
> remembering which one is which.

I don't see that we need to be consistent in the sense you propose.
We could instead be consistent in the sense we are now.

It feels quite natural to say `C-x 5 5', because here the final "5"
refers to another frame.  Whereas in `C-x 4 4', the final "4" refers to
another window.  Highly logical and consistent to me.

`C-x 4 4' is also more ergonomic.  I appreciate that, since I tend to
use this command quite a bit.



  parent reply	other threads:[~2021-10-10 23:32 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 [this message]
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=CADwFkmnoMJeUGfPS5jAbYso0fWCLOrYnWuW7FcFvnZx0mpuqYg@mail.gmail.com \
    --to=stefankangas@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).