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

[Drew Adams]

>  That the new `clone-frame' command only "Make[s] a
> new frame with the same parameters as FRAME" and doesn't
> include its window configuration seems like an anomaly

It's not an anomaly.  It's by design, as being the
most useful behavior (IMO).

But nothing precludes adding duplication of the
frame's window configuration to `clone-frame'
by way of its prefix arg.

> > Also since 'clone-frame' doesn't duplicate the frame,
> > we could add a new command 'duplicate-frame' as well.
> 
> Maybe so, but I wonder if it would be better to consistently use
> "clone" to mean "Create a twin copy of...", and use "duplicate" to mean
> something like what the `clone-frame' command currently does,
> i.e. create a copy that shares some attributes but not all.

A window config is not a frame attribute.  But
sure, the "clone" of a thing is debatable.

IMO, we shouldn't needlessly add commands, and
especially default key bindings - and what was
suggested there is needless, IMO.

Just add the requested behavior to `clone-frame'
by way of its prefix arg.  With no prefix arg
you clone the frame (new frame with same params).
With a prefix arg you clone it and reproduce its
window config.