From: Heime <heimeborgia@protonmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: RE: [External] : Send buffer to new emacs session
Date: Wed, 23 Aug 2023 05:17:17 +0000 [thread overview]
Message-ID: <h9VidPF4lW3LeLY-h1L-d9lVh8rhm5YGmcQL9NK0FGyA4V_h9PCtcQ3UF2CWCOmI3pSt3qaw2Qyir2zYhIFH8Saz1-3sO2pOOtaUUg5Hrs4=@protonmail.com> (raw)
In-Reply-To: <SJ0PR10MB548862EEAC13517E80FCD13DF31CA@SJ0PR10MB5488.namprd10.prod.outlook.com>
Sent with Proton Mail secure email.
------- Original Message -------
On Wednesday, August 23rd, 2023 at 1:30 PM, Drew Adams <drew.adams@oracle.com> wrote:
> > I have a buffer in an emacs session, call the session S1. I want to start
> > a new emacs session
> > (call it S2) with the frame displaying the current buffer in S1. All the
> > windows displaying
> > buffer in S1 are then to be removed and the buffer in S1 killed. What can
> > I do using elisp code ?
>
>
> The buffer doesn't exist in another Emacs session,
> as I mentioned when you asked the question elsewhere.
>
> If you're talking only about the buffer's content,
> or perhaps its content and some other state (e.g.
> list of markers, variable values,...), then you can
> of course persist most such info in a file and
> then populate a buffer in the other session using it.
>
> But a buffer is itself in memory, and session-specific.
The buffer is then only known with a particular session,
there is no possibility for a different emacs session to
capture the details from another emacs session. Unless
that memory is captures in a file that the new session can
read.
I understand your point. I shall keep with a new frame
associated with its respective emacs session.
> (But I said all of this the first time you asked...,
> and I pointed you to Emacs docs about buffers etc.)
next prev parent reply other threads:[~2023-08-23 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 22:30 Send buffer to new emacs session Heime
2023-08-23 1:30 ` [External] : " Drew Adams
2023-08-23 1:38 ` Drew Adams
2023-08-23 5:17 ` Heime [this message]
2023-08-23 14:13 ` Drew Adams
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='h9VidPF4lW3LeLY-h1L-d9lVh8rhm5YGmcQL9NK0FGyA4V_h9PCtcQ3UF2CWCOmI3pSt3qaw2Qyir2zYhIFH8Saz1-3sO2pOOtaUUg5Hrs4=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=drew.adams@oracle.com \
--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).