Re: On the new startup and scratch buffer

[Sascha Wilde <wilde@sha-bang.de>]

Angelo Graziosi <angelo.graziosi@alice.it> wrote:
> Jonathan Rockway ha scritto:
[...]
>> According to the docstring on `initial-scratch-message':
>>
>>    "Initial message displayed in *scratch* buffer at startup.
>>     If this is nil, no message will be displayed.
>>     If `inhibit-startup-screen' is non-nil, then no message is displayed,
>>     regardless of the value of this variable."
>>
>> So it looks like this is expected, although annoying.  This just looks
>> like a side effect of having this block:
>>
>>       (and initial-scratch-message
>> 	   (get-buffer "*scratch*")
>> 	   (with-current-buffer "*scratch*"
>> 	     (when (zerop (buffer-size))
>> 	       (insert initial-scratch-message)
>> 	       (set-buffer-modified-p nil))))
>>
>> On the "else" side of the (if (or ... inhibit-startup-screen ...) ...)
>> statement.
>>
>> If people are interested in a change to this behavior (always add text
>> to *scratch* if initial-scratch-message isn't nil), I'll supply a patch.
>>
>
> I think it would be a good thing, so I vote for it: +1.

AOL: +1

As initial-scratch-message is sufficient to disable the *scratch*
message in case one wants to, inhibit-startup-screen shouldn't do so.

cheers
sascha
-- 
Sascha Wilde

I've always figured UNIX is a utility to be run under emacs.
	-- Charles R. Martin