From xemacs-m  Mon Sep  8 12:58:24 1997
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2])
	by xemacs.org (8.8.5/8.8.5) with SMTP id MAA02641
	for <xemacs-beta@xemacs.org>; Mon, 8 Sep 1997 12:58:23 -0500 (CDT)
Received: from TEN-THOUSAND-DOLLAR-BILL.MIT.EDU by MIT.EDU with SMTP
	id AA06496; Mon, 8 Sep 97 13:58:24 EDT
Received: by ten-thousand-dollar-bill.MIT.EDU (8.8.5/4.7) id NAA08551; Mon, 8 Sep 1997 13:57:41 -0400 (EDT)
Date: Mon, 8 Sep 1997 13:57:41 -0400 (EDT)
Message-Id: <199709081757.NAA08551@ten-thousand-dollar-bill.MIT.EDU>
From: David Bakhash <cadet@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: xemacs-beta@xemacs.org
Subject: Re: saving *scratch* buffer
X-Mailer: VM 6.31 under 20.2 XEmacs Lucid

Hrvoje Niksic writes:
 > David Bakhash <cadet@MIT.EDU> writes:
 > 
 > > I am not running that version (20.3b19).  I had assumed when I saw your
 > > emails about the *scratch* buffer thing, that 20.3b19 was no different
 > > from the 20.2 XEmacs running at MIT.
 > 
 > Your assumption was correct:

 > ...and no question is asked!  This part of XEmacs has not changed
 > between 20.2 and 20.3 (except for changes in `save-some-buffers').
 > BTW, I find it curious that `C-x C-c' asks for saving, whereas `C-x s' 
 > doesn't, because `save-buffers-kill-emacs' calls `save-some-buffers'
 > to do the asking.

okay.  First off, save-some-buffers takes an optional 2nd argument
(``EXITING'') which, if non-nil, tells it to prompt for certain non-file
buffers.  That explains that.  It might be save-some-buffers, but
truthfully, I don't know anymore.  AFAI am concerned, if 20.3 doesn't
have this problem of trying to save the *scratch* buffer, then let's
just forget about it.  I don't know what's up with the version of 20.2
at school.

dave

