From: Heime <heimeborgia@protonmail.com>
To: PierGianLuca <luca@magnaspesmeretrix.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Get buffer unto a new frame
Date: Fri, 18 Aug 2023 14:10:44 +0000 [thread overview]
Message-ID: <DQbLWr6sxzS_ClBCZbQ2ATSBewyxugHFoAc3SMo-m5o3VVW_jqcSlmSwK1coVWTs6lxkBP9Gl06V8xffOvyQ49bvtKCyENzWSRlgPFfxLmc=@protonmail.com> (raw)
In-Reply-To: <2a718b7a-ad27-16d5-7f91-27708bbbf5c8@magnaspesmeretrix.org>
------- Original Message -------
On Saturday, August 19th, 2023 at 1:57 AM, PierGianLuca <luca@magnaspesmeretrix.org> wrote:
> Hi Heime,
>
> Just wanted to say I completely understand you. I've had to deal with similar
> conundrums for many years. My personal experience is that (in my case) there's
> simply no best rule. I've had situations in which I needed copies of a buffer
> in different frames (especially if the frames live in different virtual desktops),
> or copies within the same frame but different windows; different buffers in different
> frames, different buffers in the same frame, and whatnot...
Then, one should have the capability to have a number of possibilities.
> For me the optimal solution has been to set up quicker keyboard shortcuts
> (avoiding all longer "C-x ..." ones) to ease up this kind of configuration changes.
>
> Cool if you find a standard solution for the kind of work you do.
Perhaps as you say, I might require different possibilities in future.
By detach I usually mean "send it away", meaning that the buffer is
sent away to a new frame, leaving nothing behind.
One can have multiple windows of the same buffer, is that correct ?
Can one remove all windows showing same buffer in some frame ?
> I'm really happy for the extreme flexibility that Emacs gives in this regard!
>
> Cheers,
> Luca
next prev parent reply other threads:[~2023-08-18 14:10 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 [this message]
2023-08-18 14:33 ` [External] : " Drew Adams
2023-08-18 14:36 ` PierGianLuca
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='DQbLWr6sxzS_ClBCZbQ2ATSBewyxugHFoAc3SMo-m5o3VVW_jqcSlmSwK1coVWTs6lxkBP9Gl06V8xffOvyQ49bvtKCyENzWSRlgPFfxLmc=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=luca@magnaspesmeretrix.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).