unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: Re: Get buffer unto a new frame
Date: Fri, 18 Aug 2023 12:56:07 +0200	[thread overview]
Message-ID: <trinity-62764745-54ac-4541-b9b7-efc5bbe5b80b-1692356167398@3c-app-mailcom-bs01> (raw)
In-Reply-To: <63aR95kjBnrEzFE6lJM9suzyL-9i_WCsNCxKxYgFrpfCNKRsd7a3VasrDsShzVumLgkPHW3JpekQ2AVAtbwlE4nDFCmBMaGx4OcGNTeLpWU=@protonmail.com>


> Sent: Friday, August 18, 2023 at 9:59 PM
> From: "Heime" <heimeborgia@protonmail.com>
> To: "Heime via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> Subject: Get buffer unto a new frame
>
> How can I have a buffer taken out from a frame and make a new frame
> using elisp code ?

(defun detach-window ()
  "Sends the selected window to a new frame."

  (interactive)

  (let* ( (window (selected-window))
          (buf (window-buffer window))
          (frame (make-frame)) )

    (select-frame frame)
    (switch-to-buffer buf)
    (delete-window window)))


----- Christopher Dimech
Administrator General - Naiad Informatics - Gnu Project

Society has become too quick to pass judgement and declare someone
Persona Non-Grata, the most extreme form of censure a country can
bestow.

In a new era of destructive authoritarianism, I support Richard
Stallman.  Times of great crisis are also times of great
opportunity.  I call upon you to make this struggle yours as well !

https://stallmansupport.org/
https://www.fsf.org/     https://www.gnu.org





  reply	other threads:[~2023-08-18 10:56 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 [this message]
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
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=trinity-62764745-54ac-4541-b9b7-efc5bbe5b80b-1692356167398@3c-app-mailcom-bs01 \
    --to=dimech@gmx.com \
    --cc=heimeborgia@protonmail.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).