unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Howard Melman <hmelman@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Adding missing C-x 5 C-j and C-x t C-j commands
Date: Tue, 07 Jun 2022 16:17:29 -0400	[thread overview]
Message-ID: <lyzgioxm7a.fsf@Lumet.home> (raw)
In-Reply-To: 86v8twyyx9.fsf@mail.linkov.net

Juri Linkov <juri@linkov.net> writes:

>>> We have the "C-x 5 5" prefix for purposes like this one.
>>> It's a great fallback,
>>
>> It shouldn't be a fallback.  It should be "the new C-x 5" and it should
>> hopefully completely replace `C-x 5` at some point.
>
> Should the prefix `C-x 5` take keys from the `C-x` keymap?
> So any key in the `C-x` keymap will be automatically
> available in a key sequence starting with `C-x 5`?
>
> For example, `C-x C-d` is bound to `list-directory`,
> then the inferred `C-x 5 C-d` will show the output
> of `list-directory` in a new frame?

I have a question the other way.  I forgot that `C-x 5 .'
exists and tried `C-x 5 5 M-.' and was surprised to find it
didn't work (it opened in the same frame as if I just did
`M-.'.  Is it supposed to work or should I open a bug?

-- 

Howard




  reply	other threads:[~2022-06-07 20:17 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 [this message]
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=lyzgioxm7a.fsf@Lumet.home \
    --to=hmelman@gmail.com \
    --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).