From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>
Cc: juri@linkov.net, emacs-devel@gnu.org
Subject: Re: Adding missing C-x 5 C-j and C-x t C-j commands
Date: Thu, 09 Jun 2022 08:02:27 +0300 [thread overview]
Message-ID: <83pmji4efw.fsf@gnu.org> (raw)
In-Reply-To: <1DBEB800-86E1-4054-BF97-CFC10AF5C7E0@gmail.com> (message from Howard Melman on Wed, 8 Jun 2022 15:17:02 -0400)
> From: Howard Melman <hmelman@gmail.com>
> Date: Wed, 8 Jun 2022 15:17:02 -0400
> Cc: emacs-devel@gnu.org
>
> On Jun 8, 2022, at 12:08 PM, Juri Linkov <juri@linkov.net> wrote:
> >
> > I'm not sure if the default value can be changed,
> > but you are right about other-frame-prefix.
> > I didn't know that project--other-place-command
> > let binds it to t. But doing the same is not possible
> > in other-frame-prefix, that just sets a display action
> > for the next command. So a more elaborate fix is required:
>
> Seems to work for me. Any chance this could make it into a 28.2?
No, it's too late for adding such non-trivial behavior changes. We
could have unintended consequences, and we don't want to risk that on
the release branch.
Sorry.
next prev parent reply other threads:[~2022-06-09 5:02 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
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 [this message]
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=83pmji4efw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hmelman@gmail.com \
--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).