Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!cit-vax!ucla-cs!zen!ucbvax!LF-SERVER-2.BBN.COM!jr
From: jr@LF-SERVER-2.BBN.COM (John Robinson)
Newsgroups: comp.emacs
Subject: Re: kill-buffer (was: what does (put 'xxxx-mode 'mode-class 'special) do? )
Message-ID: <8709012011.AA27939@ucbvax.Berkeley.EDU>
Date: Tue, 1-Sep-87 16:11:53 EDT
Article-I.D.: ucbvax.8709012011.AA27939
Posted: Tue Sep  1 16:11:53 1987
Date-Received: Sat, 5-Sep-87 04:42:45 EDT
References: <1514@cullvax.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jr@ALEXANDER.BBN.COM
Organization: The ARPA Internet
Lines: 18

>> mayer@hplabsz.HPL.HP.COM (Niels Mayer) writes:
>> > Oh yeah, and while I've got your attention let me ask another question:
>> > what is it about the buffers created by shell-command, dired, etc. that allows
>> > kill-buffer to delete the buffer without querying the user with
>> > "Buffer xyzzy modified; kill anyway?".
>> 
>> I think it's the fact that the buffer name starts with '*'.  At least,
>> if I manually  make such a buffer (via c-X B), I can delete it without
>> it questioning me.

Nope.  If the variable buffer-file-name is nil, emacs figures you
don't care about its disposition (or if it is unmodified - no ** in
the mode line).  Otherwise, what would happen if you wnatrd to edit a
file whose name happened to begin with '*'?  (try ^X^F *foo for
kicks).

/jr
jr@bbn.com or jr@bbn.uucp