From: 李不显 <flypigonsky@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How can I restart *scratch* buffer?
Date: Sun, 8 Sep 2019 20:29:55 +0800 [thread overview]
Message-ID: <CALrvcGJeS+HeWK99+ugXmUxXtV_Zbo2XRbrk8GTNLbEm1d1uxw@mail.gmail.com> (raw)
In-Reply-To: <87v9uaogv5.fsf@mbork.pl>
Marcin Borkowski <mbork@mbork.pl> 于2019年9月2日周一 下午11:30写道：
>
> On 2019-09-02, at 14:10, 李淼 <flypigonsky@gmail.com> wrote:
>
> > Sometimes I accidentally turn off the *scratch* buffer while I'm using
> > emacs. How can I restart *scratch* buffer without restarting emacs?
>
> How about M-: (startup--get-buffer-create-scratch) RET?
>
> M-: stuff is necessary because this is a non-interactive function. It
> is also internal (because it contains two dashes) and undocumented
> (because it does not contain a docstring). Use at your own risk.
>
> Hth,
>
> --
> Marcin Borkowski
> http://mbork.pl
I tried to do this, but *backtrace* says:
Debugger entered--Lisp error: (void-function
startup-get-buffer-create-scratch)
(startup-get-buffer-create-scratch)
eval((startup-get-buffer-create-scratch) nil)
elisp--eval-last-sexp(nil)
eval-last-sexp(nil)
funcall-interactively(eval-last-sexp nil)
call-interactively(eval-last-sexp nil nil)
command-execute(eval-last-sexp)
next prev parent reply other threads:[~2019-09-08 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 12:10 How can I restart *scratch* buffer? 李淼
2019-09-02 12:22 ` YUE Daian
2019-09-02 12:24 ` YUE Daian
2019-09-02 12:33 ` Joost Kremers
2019-09-02 13:07 ` Michael Heerdegen
2019-09-02 14:15 ` Alberto Luaces
2019-09-02 14:46 ` 李不显
[not found] ` <CALrvcGLBQhJG5wtb41Y2uhx0HECvWFyeSfwvY=T8LG=1NfO0XQ@mail.gmail.com>
[not found] ` <87woeq6qgo.fsf@work.i-did-not-set--mail-host-address--so-tickle-me>
2019-09-08 12:16 ` Fwd: " 李不显
2019-09-02 15:30 ` Marcin Borkowski
2019-09-08 12:29 ` 李不显 [this message]
2019-09-08 12:56 ` Amin Bandali
2019-09-08 13:25 ` Stefan Monnier
2019-09-08 19:59 ` Marcin Borkowski
2019-09-08 20:21 ` 李不显
2019-09-08 20:32 ` 李不显
2019-09-08 20:43 ` 李不显
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=CALrvcGJeS+HeWK99+ugXmUxXtV_Zbo2XRbrk8GTNLbEm1d1uxw@mail.gmail.com \
--to=flypigonsky@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/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).