From: Heime <heimeborgia@protonmail.com>
To: tomas@tuxteam.de
Cc: alexbuhl <alexbuhl@protonmail.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: The real difference between get-buffer-create and with-output-to-temp-buffer
Date: Thu, 05 Sep 2024 11:27:02 +0000 [thread overview]
Message-ID: <lqO_zXGGNPhxbURM2uUEYqOJJBSe8sK05PnqkZgtSFOmFjzZYU8yQUDs286cCNO8PcuHRWRANZm0azpWFQQo2tQCKYRJsf1OkLAnHjBOfrM=@protonmail.com> (raw)
In-Reply-To: <Ztk1h4YotadHLXMZ@tuxteam.de>
On Thursday, September 5th, 2024 at 4:37 PM, tomas@tuxteam.de <tomas@tuxteam.de> wrote:
> On Wed, Sep 04, 2024 at 10:11:11PM +0000, alexbuhl via Users list for the GNU Emacs text editor wrote:
>
> > Is there a real difference between doing
> >
> > (get-buffer-create "Questor")
> >
> > and
> >
> > (with-output-to-temp-buffer "Questor"
>
>
> With-output-to-temp-buffer calls get-buffer-create and redirects standard
> output to it.
>
> If you want to do /other/ things with your new buffer, you'll need the
> first function.
Including text properties seems to make with-output-to-temp-buffer fail.
Are text properties part of those other things where I would need
get-buffer-create ?
> Try looking up its docstring (C-h f with-output-to-temp-buffer), perhaps
> follow the link to its source. It's short and sweet.
>
> Cheers
> --
> t
prev parent reply other threads:[~2024-09-05 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 22:11 The real difference between get-buffer-create and with-output-to-temp-buffer alexbuhl via Users list for the GNU Emacs text editor
2024-09-05 4:37 ` tomas
2024-09-05 11:27 ` Heime [this message]
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='lqO_zXGGNPhxbURM2uUEYqOJJBSe8sK05PnqkZgtSFOmFjzZYU8yQUDs286cCNO8PcuHRWRANZm0azpWFQQo2tQCKYRJsf1OkLAnHjBOfrM=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=alexbuhl@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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).