unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 34715@debbugs.gnu.org
Subject: bug#34715: 26.1; (1) Add `clone-frame', (2) bind it to `C-x 5 2'
Date: Mon, 04 Mar 2019 18:12:21 +0200	[thread overview]
Message-ID: <83sgw2ehzu.fsf@gnu.org> (raw)
In-Reply-To: <17bef02b-7dd4-4086-828f-59488a836ac1@default> (message from Drew Adams on Sat, 2 Mar 2019 16:47:47 -0800 (PST))

> Date: Sat, 2 Mar 2019 16:47:47 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> 
> 1. Add a `clone-frame' command such as this one, which is similar to
>    what I've been using:
> 
> (defun clone-frame (&optional frame no-clone)
>   "Make a new frame with the same parameters as FRAME.
> With a prefix arg, don't clone - just call `make-frame-command'.
> 
> FRAME defaults to the selected frame.  The frame is created on the
> same terminal as FRAME.  If the terminal is a text-only terminal then
> also select the new frame."
>   (interactive "i\nP")
>   (if no-clone
>       (make-frame-command)
>     (let* ((default-frame-alist  (frame-parameters frame))
>            (new-fr               (make-frame)))
>       (unless (display-graphic-p) (select-frame new-fr))
>       new-fr)))
> 
> 2. Use it, not `make-frame-command', as the binding of `C-x 5 2'.

I'm okay with adding a new command, but rebinding "C-x 5 2" by default
at the same time is a non-starter.  We should first let people use the
new command, and should see how many of them ask to change the default
binding.

>    Why change the default behavior of `C-x 5 2'?  If I want the buffer
>    of the selected window shown in another frame then I typically want
>    that frame to have the same parameters.

That's what default-frame-alist is for.  If you are used to change the
parameters of your frames a lot during their lifetime, which
presumably means each of your frames might look and work differently,
it is not entirely clear to me that "C-x 5 2" should produce a clone
of the random frame where you just happened to type the command.  It
could even cause trouble/unexpected behavior, with some exotic
parameters, at least in principle.

So I think we definitely should collect more experience before
changing this veteran binding.

> 3. BTW, I think it would be good to add this to the doc string of
>    `make-frame-command':
> 
>    Return the new frame.

"When called from Lisp, return the new frame."





  reply	other threads:[~2019-03-04 16:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03  0:47 bug#34715: 26.1; (1) Add `clone-frame', (2) bind it to `C-x 5 2' Drew Adams
2019-03-04 16:12 ` Eli Zaretskii [this message]
2019-03-08  9:46 ` Eli Zaretskii
2021-09-01  9:43 ` bug#32736: 26; Bind `C-x 5 2' to `clone-frame' by default Lars Ingebrigtsen
2021-09-01 12:47   ` bug#34715: " Eli Zaretskii
2021-09-01 12:53     ` bug#32736: " Lars Ingebrigtsen
2021-09-01 13:38       ` Eli Zaretskii
2021-09-01 13:40         ` Lars Ingebrigtsen
2021-09-01 13:41           ` Lars Ingebrigtsen
2021-09-01 13:55             ` Lars Ingebrigtsen
2021-09-01 14:11               ` Eli Zaretskii
2021-09-01 14:18                 ` Lars Ingebrigtsen
2021-09-01 14:28                   ` bug#34715: " Lars Ingebrigtsen
2021-09-01 15:57                   ` Eli Zaretskii
2021-09-02  7:44                     ` Lars Ingebrigtsen
2021-09-02  7:51                       ` Eli Zaretskii
2021-09-02  8:01                         ` bug#34715: " Lars Ingebrigtsen
2021-09-02  8:19                           ` Eli Zaretskii
2021-09-02  8:57                             ` Lars Ingebrigtsen
2021-09-02 12:03                               ` Eli Zaretskii
2021-09-02 16:05                                 ` bug#34715: " Lars Ingebrigtsen
     [not found] <<17bef02b-7dd4-4086-828f-59488a836ac1@default>
     [not found] ` <<83sgw2ehzu.fsf@gnu.org>
2019-03-04 17:25   ` bug#34715: 26.1; (1) Add `clone-frame', (2) bind it to `C-x 5 2' Drew Adams
2019-03-04 18:14     ` Eli Zaretskii
2019-03-30 21:58     ` 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=83sgw2ehzu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34715@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).