From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Adding missing C-x 5 C-j and C-x t C-j commands
Date: Sun, 22 May 2022 21:57:22 -0700 [thread overview]
Message-ID: <871qwkyhfx.fsf@athena.silentflame.com> (raw)
In-Reply-To: <83fsl16l5l.fsf@gnu.org>
Hello,
On Mon 23 May 2022 at 05:24am +03, Eli Zaretskii wrote:
>> From: Sean Whitton <spwhitton@spwhitton.name>
>> Date: Sun, 22 May 2022 12:53:25 -0700
>>
>> We have C-x d, C-x 4 d, C-x 5 d and C-x t d, but only C-x C-j
>> and C-x 4 C-j. My fingers try to use C-x 5 C-j, and find it isn't
>> there, at least biweekly. Here is a draft patch to fill the gap.
>
> We have the "C-x 5 5" prefix for purposes like this one.
It's a great fallback, but in this case I don't think one should have to
use it. For everything else under C-x 4 for which -other-frame and
-other-tab variants make sense, we also have bindings under C-x 5 and
C-x t. If we miss some of them out because we've since added C-x 5 5,
we are asking the user to keep track of which things under C-x 4 have
bindings under C-x 5 and which don't -- one has to remember that C-x 4
C-j exists but C-x 5 C-j doesn't. I'd prefer that we don't impose that
cognitive burden on users just because we now have C-x 5 5.
--
Sean Whitton
next prev parent reply other threads:[~2022-05-23 4:57 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qwkyhfx.fsf@athena.silentflame.com \
--to=spwhitton@spwhitton.name \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.