unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: "C-x 5 5" vs "C-x 4 1" inconsistency
Date: Sun, 10 Oct 2021 20:15:14 +0300	[thread overview]
Message-ID: <871r4sby3h.fsf@mail.linkov.net> (raw)
In-Reply-To: <83bl3xrwl0.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Oct 2021 13:41:15 +0300")

>> >> 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'.
>
> But other-frame-prefix is "C-x 5 5".  This is inconsistent with other
> uses of these prefixes, specifically "C-x 5 2", "C-x 5 b", C-x 5 f",
> which have their "C-x 4" counterparts.

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.

Recently Drew mentioned that there is the command 'tear-off-window'.
It would perfectly fit into the keybinding 'C-x 4 5' with mnemonics
that '4' (window) is detached to '5' (frame):

diff --git a/lisp/window.el b/lisp/window.el
index 971264b634..2fd9c970b0 100644
--- a/lisp/window.el
+++ b/lisp/window.el
@@ -10381,6 +10381,7 @@ ctl-x-map
 (define-key ctl-x-4-map "0" 'kill-buffer-and-window)
 (define-key ctl-x-4-map "1" 'same-window-prefix)
 (define-key ctl-x-4-map "4" 'other-window-prefix)
+(define-key ctl-x-4-map "5" 'tear-off-window)
 
 (defvar other-window-repeat-map
   (let ((map (make-sparse-keymap)))
-- 



  parent reply	other threads:[~2021-10-10 17:15 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 [this message]
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=871r4sby3h.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=eliz@gnu.org \
    --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).