unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: emacs-devel@gnu.org, juri@linkov.net
Subject: Re: Adding missing C-x 5 C-j and C-x t C-j commands
Date: Mon, 23 May 2022 17:07:37 +0300	[thread overview]
Message-ID: <83v8tw5oly.fsf@gnu.org> (raw)
In-Reply-To: <87o7zowe0j.fsf@athena.silentflame.com> (message from Sean Whitton on Mon, 23 May 2022 06:54:20 -0700)

> From: Sean Whitton <spwhitton@spwhitton.name>
> Date: Mon, 23 May 2022 06:54:20 -0700
> 
> I certainly agree with you that we shouldn't bind things into C-x 5
> willy-nilly.  In this case, however, it's not just because we can, but
> because it makes things consistent with C-x 4 in a way that's helpful.

My point is that it may be useful for you, but is not necessarily
useful enough for others to justify a global "C-x 5" binding.

> As Juri has determined, it's almost the only one that doesn't match
> right now.

"C-x 4 a" is also unpaired, as are "C-x 5 u", "C-x 5 2", and "C-x 5 o".
That's hardly "almost".

> Here's a different way to look at it.  Given the existing symmetry
> between C-x 4 and C-x 5, if we later bind anything *other* than
> dired-jump-other-window to C-x 5 C-j, we would be introducing a special
> exception that users would have to remember.  That is, the existing
> symmetry has already implicitly semi-reserved C-x 5 C-j for
> dired-jump-other-window, by giving us a strong reason not to put
> anything else there.

See above: we already have asymmetry.



  reply	other threads:[~2022-05-23 14:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 19:53 Adding missing C-x 5 C-j and C-x t C-j commands Sean Whitton
2022-05-23  2:24 ` Eli Zaretskii
2022-05-23  4:57   ` Sean Whitton
2022-05-23  4:59     ` Sean Whitton
2022-05-23  7:56       ` Juri Linkov
2022-05-23  9:16         ` Eli Zaretskii
2022-05-23 13:54           ` Sean Whitton
2022-05-23 14:07             ` Eli Zaretskii [this message]
2022-05-23 20:52               ` Sean Whitton
2022-05-23 13:35         ` Sean Whitton
2022-05-23 12:26     ` Stefan Monnier
2022-05-23 16:52       ` Juri Linkov
2022-06-07 20:17         ` Howard Melman
2022-06-08  2:29           ` Eli Zaretskii
2022-06-08  6:40           ` Juri Linkov
2022-06-08 12:27             ` Howard Melman
2022-06-08 16:08               ` Juri Linkov
2022-06-08 19:17                 ` Howard Melman
2022-06-09  2:41                   ` Howard Melman
2022-06-09  6:44                     ` Juri Linkov
2022-06-09  5:02                   ` Eli Zaretskii
2022-06-09  6:42                     ` Juri Linkov

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=83v8tw5oly.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=spwhitton@spwhitton.name \
    /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).