From xemacs-m  Mon Aug 11 13:53:56 1997
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA23568
	for <xemacs-beta@xemacs.org>; Mon, 11 Aug 1997 13:53:55 -0500 (CDT)
Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA17895 for <xemacs-beta@xemacs.org>; Mon, 11 Aug 1997 11:53:22 -0700
Received: from legba.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3)
	id LAA09793; Mon, 11 Aug 1997 11:53:17 -0700
Received: by legba.Corp.Sun.COM (SMI-8.6/SMI-SVR4)
	id LAA26159; Mon, 11 Aug 1997 11:48:27 -0700
To: xemacs-beta@xemacs.org
Subject: initial scratch message
X-Attribution: GDF
Mail-Copies-To: never
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Gary.Foster@Corp.Sun.COM (Gary D. Foster)
Date: 11 Aug 1997 11:48:26 -0700
Message-ID: <bcipvrko8sl.fsf@corp.Sun.COM>
Lines: 9
X-Mailer: Gnus v5.4.64/XEmacs 20.3(beta17) - "Bucharest"

I feel that (setq initial-scratch-message nil) should work to set the
scratch buffer message to nothing.  However, setting this causes an
error plonk the first time the buffer is created (I can provide a
backtrace if necessary, although it's pretty easy to determine why).

Should this behavior be changed to allow setting it to nil?  I have it 
set to "" now, which doesn't generate the error.

-- Gary F.

