unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Kamphausen <skampi@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: *scratch* lost
Date: Wed, 17 Jun 2009 13:03:10 +0200	[thread overview]
Message-ID: <87zlc76s29.fsf@usenet.my.skamphausen.de> (raw)
In-Reply-To: 7cr5xlyeui.fsf@pbourguignon.anevia.com

Hi,

pjb@informatimago.com (Pascal J. Bourguignon) writes:

> "B. T. Raven" <nihil@nihilo.net> writes:
>
>> I was doing some key mapping in .emacs and instead of saving the file,
>> restarting Emacs, and testing the new assignment I was doing M-x eval
>> region on changed areas of .emacs Somehow all (or many) keychords
>> started acting strangely, e.g. C-x 1 would open subr.el in a new
>> buffer instead of showing current buffer alone in frame, even cursor
>> movement keys did something else. I killed .emacs buffer without
>> saving (losing changes) and then exited Emacs. On restarting
>> everything looks and works normally exept that *scratch* is empty
>> (three commented lines are missing) and it is in Fundamental mode
>> instead of Lisp Interaction. Can I get the old *scratch* buffer back?
>> How?

Maybe you somehow interfered with the variables

* inhibit-startup-screen
* initial-scratch-message

? 

>
> (defun make-scratch ()

[...]

>     (emacs-lisp-mode))))
>
>
> M-x make-scratch RET

Hm, I don't seem to need that.  I can always M-x switch-to-buffer
*scratch* RET (having to type "*scratch*" without completion since it
may have been killed) and end up in a perfect stracth-buffer with
lisp-interaction-mode.  It even works with iswitchb-buffer which asks
before creating the new buffer.


Cheers,
Stefan
-- 
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.


  parent reply	other threads:[~2009-06-17 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13 16:20 *scratch* lost B. T. Raven
2009-06-13 16:40 ` B. T. Raven
2009-06-15 10:24 ` Pascal J. Bourguignon
2009-06-15 15:31   ` B. T. Raven
2009-06-17 11:03   ` Stefan Kamphausen [this message]
2009-06-17 11:36     ` Pascal J. Bourguignon
2009-06-17 11:49       ` Stefan Kamphausen
2009-06-17 12:25         ` B. T. Raven
2009-06-17 14:12           ` Rancier, Jeffrey
2009-06-17 18:14         ` Johan Bockgård

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=87zlc76s29.fsf@usenet.my.skamphausen.de \
    --to=skampi@gmx.net \
    --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).