From: Juri Linkov <juri@linkov.net>
To: "Kocken\, I.J. \(Ilja\)" <I.J.Kocken@uu.nl>
Cc: 35466@debbugs.gnu.org
Subject: bug#35466: 26.2; Feature request: add clone-indirect-buffer-other-frame to C-x 5 c
Date: Wed, 29 May 2019 00:41:23 +0300 [thread overview]
Message-ID: <87r28ib6kc.fsf@mail.linkov.net> (raw)
In-Reply-To: <87r29ngg90.fsf@uu.nl> (I. J. Kocken's message of "Sat, 27 Apr 2019 23:50:20 +0000")
> Not so much a bug, as a feature request. But upon reading that the very
> useful C-x 4 c is bound to `clone-indirect-buffer-other-window`[1] on
> reddit [2], and that the C-x 5 prefix is usually linked to frame related
> commands, I was hoping to see that C-x 5 c would create an indirect
> buffer copy in a new frame (since I rely on frames-only-mode and my
> winowmanager sway for moving between frames). I was sad to see this
> didn't exist yet, but glad that by looking at the source code I could
> whip a working function up very quickly:
>
> (defun clone-indirect-buffer-other-frame (newname display-flag &optional norecord)
> "Like `clone-indirect-buffer' but display in another frame."
> (interactive
> (progn
> (if (get major-mode 'no-clone-indirect)
> (error "Cannot indirectly clone a buffer in %s mode" mode-name))
> (list (if current-prefix-arg
> (read-buffer "Name of indirect buffer: " (current-buffer)))
> t)))
> (let ((pop-up-frames t))
> (clone-indirect-buffer newname display-flag norecord)))
>
> I think adding this to emacs, bound to C-x 5 c, would create a
> more consistent interface. I hope you agree!
The only problem with this binding is that bug#34715 proposed
to use the same binding C-x 5 c for clone-frame.
next prev parent reply other threads:[~2019-05-28 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 23:50 bug#35466: 26.2; Feature request: add clone-indirect-buffer-other-frame to C-x 5 c Kocken, I.J. (Ilja)
2019-05-28 21:41 ` Juri Linkov [this message]
2021-02-01 9:46 ` Lars Ingebrigtsen
2021-02-02 17:32 ` Ilja Kocken
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r28ib6kc.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=35466@debbugs.gnu.org \
--cc=I.J.Kocken@uu.nl \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.