From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: Adam Porter <adam@alphapapa.net>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: [PATCH] New tab-bar-detach-tab command
Date: Wed, 6 Oct 2021 20:20:01 +0000 [thread overview]
Message-ID: <SJ0PR10MB54880C28F6047053B995C0E9F3B09@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87v92ase7i.fsf_-_@mail.linkov.net>
> > When I say that `clone-frame's prefix arg could
> > be used to get the behavior you're requesting
> > (clone the frame & duplicate its window config),
> > I mean that the prefix arg could do more than one
> > thing - there are different kinds of prefix args.
>
> Now 'clone-frame' was fixed to clone the window
> config and to use the prefix arg.
>
> But I'm not sure if 'clone-frame' should be rebound
> from 'C-x 5 c' to 'C-x 5 n', like 'clone-buffer' is
> bound to 'C-x x n',and 'tab-duplicate' is bound to
> 'C-x t n'.
(In Info, `clone-buffer' is bound to `M-n', BTW.
And in Emacs prior to 28, at least, it has _no_
global binding.)
IMHO, there's no reason to keep giving `C-x 5 2`
to `make-frame-command`. All of the following
should be on the same key, distinguished by
default behavior versus different prefix-arg
behaviors:
* `make-frame-command' (or no longer give it any key)
* `clone-frame' - frame parameters
* `clone-frame' - frame parameters and window config
And all of that makes sense on `C-x 5 2', IMO.
The `2' is pretty naturally mnemonic for
duplicating/cloning/splitting.
In any case, I'd like to see only a single key
consumed by these make-a-frame behaviors, not
_both_ `C-x 5 2' and `C-x 5 <something else>'.
next prev parent reply other threads:[~2021-10-06 20:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 19:09 [PATCH] New tab-bar-detach-tab command Adam Porter
2021-09-29 1:05 ` Matt Beshara
2021-09-29 7:11 ` Juri Linkov
2021-09-29 7:43 ` Adam Porter
2021-09-29 7:09 ` Juri Linkov
2021-09-29 7:59 ` Adam Porter
2021-09-29 19:43 ` Juri Linkov
2021-09-29 19:54 ` Adam Porter
2021-10-03 17:19 ` Juri Linkov
2021-10-04 10:34 ` Adam Porter
2021-10-04 17:33 ` Juri Linkov
2021-10-04 19:53 ` Adam Porter
2021-10-05 6:49 ` Juri Linkov
2021-10-05 7:17 ` Adam Porter
2021-10-05 15:27 ` [External] : " Drew Adams
2021-10-05 16:38 ` Juri Linkov
2021-10-06 11:23 ` Adam Porter
2021-10-06 16:38 ` Juri Linkov
2021-10-07 18:02 ` Juri Linkov
2021-10-07 18:23 ` [External] : " Drew Adams
2021-10-05 15:18 ` Drew Adams
2021-10-05 16:40 ` Juri Linkov
2021-10-05 17:27 ` Drew Adams
2021-10-06 16:39 ` Juri Linkov
2021-10-06 20:20 ` Drew Adams [this message]
2021-10-07 7:29 ` [External] : " Juri Linkov
2021-10-07 7:43 ` Eli Zaretskii
2021-10-07 17:58 ` Juri Linkov
2021-10-07 18:19 ` Drew Adams
2021-10-07 18:28 ` Eli Zaretskii
2021-10-07 15:56 ` Drew Adams
2021-10-05 16:35 ` Juri Linkov
2021-10-05 15:15 ` [External] : " Drew Adams
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=SJ0PR10MB54880C28F6047053B995C0E9F3B09@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--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).