* Bringing back a scratch buffer ?
@ 2019-12-04 14:55 jonetsu
2019-12-04 15:14 ` tomas
0 siblings, 1 reply; 5+ messages in thread
From: jonetsu @ 2019-12-04 14:55 UTC (permalink / raw)
To: help-gnu-emacs
Simple question: If the scratch buffer gets inadvertently deleted, is it
possible to bring it back ?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bringing back a scratch buffer ?
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
0 siblings, 2 replies; 5+ messages in thread
From: tomas @ 2019-12-04 15:14 UTC (permalink / raw)
To: help-gnu-emacs
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
On Wed, Dec 04, 2019 at 09:55:17AM -0500, jonetsu wrote:
> Simple question: If the scratch buffer gets inadvertently deleted, is it
> possible to bring it back ?
Depends on what you mean by "bring back" :-)
There /is/ an internal function startup--get-buffer-create-scratch which
creates a *scratch* buffer and puts it in elisp interaction mode. The
nice and warm welcome text won't be there, though.
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.
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bringing back a scratch buffer ?
2019-12-04 15:14 ` tomas
@ 2019-12-04 15:18 ` jonetsu
2019-12-04 16:16 ` Michael Heerdegen
1 sibling, 0 replies; 5+ messages in thread
From: jonetsu @ 2019-12-04 15:18 UTC (permalink / raw)
To: help-gnu-emacs
On Wed, 4 Dec 2019 16:14:16 +0100
<tomas@tuxteam.de> wrote:
> 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.
Thanks ! Did not know about that - quite helpful.
Cheers.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bringing back a scratch buffer ?
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
1 sibling, 1 reply; 5+ messages in thread
From: Michael Heerdegen @ 2019-12-04 16:16 UTC (permalink / raw)
To: tomas; +Cc: help-gnu-emacs
<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).
Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bringing back a scratch buffer ?
2019-12-04 16:16 ` Michael Heerdegen
@ 2019-12-04 16:20 ` tomas
0 siblings, 0 replies; 5+ messages in thread
From: tomas @ 2019-12-04 16:20 UTC (permalink / raw)
To: Michael Heerdegen; +Cc: help-gnu-emacs
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-12-04 16:20 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).