unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Bringing back a scratch buffer ?
Date: Wed, 4 Dec 2019 10:18:09 -0500	[thread overview]
Message-ID: <20191204101809.5d110067@mistral> (raw)
In-Reply-To: <20191204151416.GA30361@tuxteam.de>

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.



  reply	other threads:[~2019-12-04 15:18 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 [this message]
2019-12-04 16:16   ` Michael Heerdegen
2019-12-04 16:20     ` 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=20191204101809.5d110067@mistral \
    --to=jonetsu@teksavvy.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).