[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: Thu, 7 Oct 2021 15:56:33 +0000

> > * `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.
> But a new prefix arg could be added to `make-frame-command'
> without rebinding its key `C-x 5 2'.  Then `make-frame-command'
> could call `clone-frame' after typing `C-u C-x 5 2'.

It doesn't matter to me how it's done, as long
as only one key (`C-x 5 2') is sacrificed for
these 3 related behaviors, and as long as we
nevertheless provide separate commands, for
users who do want to bind different behaviors
to different keys.

> But I wonder how the prefix arg of `C-u C-x 5 2' would be more
> discoverable than the new key `C-x 5 c'?  The doc string
> of `make-frame-command' could mention both: the prefix arg
> that clones the frame, and `clone-frame' bound to `C-x 5 c'.

Discoverability is one thing.  I don't see it
as a big problem in what I proposed.  At least
as important, I think, is needlessly wasting
key bindings.

Discoverability is not only about keys; it's
about behaviors, and commands that realize them.

reply via email to

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