Path: utzoo!attcan!uunet!decwrl!orc!inews!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.emacs
Subject: Re: %% vs. @@
Message-ID: <1990Jul6.185406.6077@iwarp.intel.com>
Date: 6 Jul 90 18:54:06 GMT
References: <87.P022y01JM01@JUTS.ccc.amdahl.com> <1990Jun27.145013.29422@talos.pm.com> <8fbY022v01fw01@JUTS.ccc.amdahl.com> <793@sono.UUCP>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 17
In-Reply-To: holley@sono.UUCP (Greg Holley)

In article <793@sono.UUCP>, holley@sono (Greg Holley) writes:
| Note:	This stream (with its rather unintuitive title) concernt a 
| 	possible EMACS mode that would allow editing of a buffer, but never
| 	write changes to a file.  This is different from the current read-only
| 	mode, which doesn't allow the buffer to be changed.
| 
| It seems to me that the best way to implement this would be via
| write-file-hooks.  Simply write a routine that checks a boolean variable
| to see if the buffer in question is non-writeable, and return t if
| non-writeable.  Then call that routine via write-file-hooks. 

Or even simpler, just (setq buffer-file-name nil).  Too easy.
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/