[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Scratch buffer annoyance
From: |
Robert J. Chassell |
Subject: |
Re: Scratch buffer annoyance |
Date: |
Wed, 18 Jul 2007 15:53:24 +0000 (UTC) |
2. provide a variable to set the *scratch* buffer's initial
major mode to lisp-interaction-mode.
initial-major-mode.
* The name of the variable initial-major-mode could mislead; and,
* the if clause that implements initial-major-mode fails unless the
`*scratch*' buffer is in Fundamental mode.
(That is what the clause should do. It is documented. Normally,
the buffer is in Lisp Interaction mode. Unfortunately, the Emacs
Lisp for the clause tells us that one of the proposals, as written,
prevents resetting the mode of the `*scratch*' buffer.)
Firstly, the documentation for the `*scratch*' buffer says
Major mode command symbol to use for the initial `*scratch*' buffer.
which suggests the possibility that `initial' has priority over `*scratch*'.
Secondly, emacs/lisp/startup.el says,
;; If *scratch* exists and init file didn't change its mode, initialize it.
(if (get-buffer "*scratch*")
(with-current-buffer "*scratch*"
(if (eq major-mode 'fundamental-mode)
(funcall initial-major-mode))
;; Don't lose text that users type in *scratch*.
(setq buffer-offer-save t)
(auto-save-mode 1)))
If the major mode is Text, the clause will not change the major mode
to the value of initial-major-mode.
There are many people who never bother to read anything. I understand
that. Also, I understand that the goal is to change Emacs so they do
not lose because of their lack of reading. That is fine.
I just want to make sure that I can return to the traditional,
documented intent of `*scratch*'. Lightning burnt out a mother board
last summer and even though I have surge protectors, I am turning off
and unplugging this computer when the weather looks dicey and I am
going away or to sleep. Also, I frequently test a new CVS snapshot of
Emacs by doing work on it. So I am often running into `*scratch*'
buffer annoyance and would like to end that.
--
Robert J. Chassell GnuPG Key ID: 004B4AC8
address@hidden address@hidden
http://www.rattlesnake.com http://www.teak.cc
- Re: Scratch buffer annoyance, (continued)
- Re: Scratch buffer annoyance, Alfred M. Szmidt, 2007/07/16
- Re: Scratch buffer annoyance, Richard Stallman, 2007/07/17
- Re: Scratch buffer annoyance, David Reitter, 2007/07/17
- Re: Scratch buffer annoyance, Tassilo Horn, 2007/07/17
- Re: Scratch buffer annoyance, Johan Bockgård, 2007/07/17
- Re: Scratch buffer annoyance, David Reitter, 2007/07/17
- Re: Scratch buffer annoyance, Tassilo Horn, 2007/07/17
- Re: Scratch buffer annoyance, Robert J. Chassell, 2007/07/17
- Re: Scratch buffer annoyance, David Reitter, 2007/07/17
- Re: Scratch buffer annoyance, Richard Stallman, 2007/07/18
- Re: Scratch buffer annoyance,
Robert J. Chassell <=
- Re: Scratch buffer annoyance, Alfred M. Szmidt, 2007/07/17
- Re: Scratch buffer annoyance, Tassilo Horn, 2007/07/17
- Re: Scratch buffer annoyance, Alfred M. Szmidt, 2007/07/17
- Re: Scratch buffer annoyance, David Kastrup, 2007/07/17
- Re: Scratch buffer annoyance, David Reitter, 2007/07/17
- Re: Scratch buffer annoyance, Richard Stallman, 2007/07/18
- Re: Scratch buffer annoyance, David Kastrup, 2007/07/18
- Re: Scratch buffer annoyance, Richard Stallman, 2007/07/19
- Re: Scratch buffer annoyance, Alfred M. Szmidt, 2007/07/17
- Re: Scratch buffer annoyance, David Kastrup, 2007/07/17