From: tomas@tuxteam.de
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Bringing back a scratch buffer ?
Date: Wed, 4 Dec 2019 17:20:55 +0100 [thread overview]
Message-ID: <20191204162055.GC30361@tuxteam.de> (raw)
In-Reply-To: <87blsom5gb.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On Wed, Dec 04, 2019 at 05:16:36PM +0100, Michael Heerdegen wrote:
> <tomas@tuxteam.de> writes:
>
> > Coming from the other side, you can just have a buffer named *scratch*
> > created by just "changing into it" (i.e. C-x b *scratch* <enter>). It
> > won't be in Lisp interaction mode, though.
>
> It will (at least in my version of Emacs).
You're right: if the (new) buffer is named *scratch* it is.
Thanks, cheers
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2019-12-04 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 14:55 Bringing back a scratch buffer ? jonetsu
2019-12-04 15:14 ` tomas
2019-12-04 15:18 ` jonetsu
2019-12-04 16:16 ` Michael Heerdegen
2019-12-04 16:20 ` tomas [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=20191204162055.GC30361@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.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).