[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [External] : Re: [PATCH] New tab-bar-detach-tab command

From: Drew Adams
Subject: RE: [External] : Re: [PATCH] New tab-bar-detach-tab command
Date: Wed, 6 Oct 2021 20:20:01 +0000

> > 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

* `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

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>'.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]