From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime Newsgroups: gmane.emacs.help Subject: RE: [External] : Send buffer to new emacs session Date: Wed, 23 Aug 2023 05:17:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30617"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Heime via Users list for the GNU Emacs text editor To: Drew Adams Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Aug 23 07:18:53 2023 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qYgGb-0007fQ-NL for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 23 Aug 2023 07:18:53 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qYgFM-0006Bf-MT; Wed, 23 Aug 2023 01:17:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qYgFJ-0005g3-Jw for help-gnu-emacs@gnu.org; Wed, 23 Aug 2023 01:17:33 -0400 Original-Received: from mail-4324.protonmail.ch ([185.70.43.24]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qYgFG-0000yL-Qm for help-gnu-emacs@gnu.org; Wed, 23 Aug 2023 01:17:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1692767847; x=1693027047; bh=tK4GBw7B5f570KWKhqPAm4L4l06tGabovfuxhCUjrWU=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=JlEmXA1jJdcWNfxbCJ4HBdH5UsEujo4Cn4BM6nNqB1EizStqqPnyqgvlAh1YkIQt8 ua7VvH7KA3+/d8AmZrVto3kTV7jVp6Jdk8X4xn9NCFrMD5X08IZ1o5VAjfTR0/HWvm xhBKHO61VfgK/RzJ+MmSc7haKc9oujFiNAEUYUh2xQ0bYvifTTDOUurHgkM8P3MA4+ E0WtIRvdr4AVGbapns0QeGP12QqtabymtopfcCDj54dhiJQoQ90SCwUaX+PO2Q1joG fKmR8rlJf9/xLh8mJ0J+eNee/grjN4w/wh36dLC/RCU/722ZIhuqZ5fr0losQbfLp7 cgnpG+ehTsNEg== In-Reply-To: Feedback-ID: 57735886:user:proton Received-SPF: pass client-ip=185.70.43.24; envelope-from=heimeborgia@protonmail.com; helo=mail-4324.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:144935 Archived-At: Sent with Proton Mail secure email. ------- Original Message ------- On Wednesday, August 23rd, 2023 at 1:30 PM, Drew Adams wrote: > > I have a buffer in an emacs session, call the session S1. I want to sta= rt > > a new emacs session > > (call it S2) with the frame displaying the current buffer in S1. All th= e > > windows displaying > > buffer in S1 are then to be removed and the buffer in S1 killed. What c= an > > I do using elisp code ? >=20 >=20 > The buffer doesn't exist in another Emacs session, > as I mentioned when you asked the question elsewhere. >=20 > 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. >=20 > 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.=20 =20 > (But I said all of this the first time you asked..., > and I pointed you to Emacs docs about buffers etc.)