From: PierGianLuca <luca@magnaspesmeretrix.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Get buffer unto a new frame
Date: Fri, 18 Aug 2023 16:36:00 +0200 [thread overview]
Message-ID: <25b59cd8-23e9-cf1c-1fe3-fef017a48fc9@magnaspesmeretrix.org> (raw)
In-Reply-To: <DQbLWr6sxzS_ClBCZbQ2ATSBewyxugHFoAc3SMo-m5o3VVW_jqcSlmSwK1coVWTs6lxkBP9Gl06V8xffOvyQ49bvtKCyENzWSRlgPFfxLmc=@protonmail.com>
On 230818 16:10, Heime wrote:
> Perhaps as you say, I might require different possibilities in future.
Or perhaps not. It's very case-dependent.
> By detach I usually mean "send it away", meaning that the buffer is
> sent away to a new frame, leaving nothing behind.
I have F12 bound to 'make-frame-command (also C-x52), which opens the buffer I'm in into a new frame – but also leaves it in the previous frame/window.
But you could bound it to 'tear-off-window instead. This would move the buffer to a new frame and close its window in the previous frame (only if there are also other windows there).
> One can have multiple windows of the same buffer, is that correct ?
Yes, even within the same frame. Very useful for example when you have to compare the beginning and end of a long file.
> Can one remove all windows showing same buffer in some frame ?
This I don't know how to do right now. But I'm sure that it can be achieved, worst case by defining some lisp function. 'kill-buffer-and-window only eliminates one of the windows showing the buffer; if there are others, they will stay but will show other buffers.
Cheers,
Luca
next prev parent reply other threads:[~2023-08-18 14:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 9:59 Get buffer unto a new frame Heime
2023-08-18 10:56 ` Christopher Dimech
2023-08-18 13:08 ` Tassilo Horn
2023-08-18 13:12 ` Yuri Khan
2023-08-18 13:41 ` Heime
2023-08-18 13:57 ` PierGianLuca
2023-08-18 14:10 ` Heime
2023-08-18 14:33 ` [External] : " Drew Adams
2023-08-18 14:36 ` PierGianLuca [this message]
2023-08-18 16:38 ` Yuri Khan
2023-08-24 16:01 ` tpeplt
2023-08-24 16:13 ` Corwin Brust
2023-08-24 16:20 ` Yuri Khan
2023-08-24 17:23 ` Richard Kerry via Users list for the GNU Emacs text editor
2023-08-25 20:24 ` tpeplt
2023-08-26 5:41 ` tomas
2023-08-26 8:28 ` Yuri Khan
2023-08-26 9:22 ` tomas
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=25b59cd8-23e9-cf1c-1fe3-fef017a48fc9@magnaspesmeretrix.org \
--to=luca@magnaspesmeretrix.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).