🚀 go-pugleaf

Greetings --

	One of my users has encountered a rather disturbing bug in GNU
EMACS 18.55 running under VMS 5.3-1.  This bug can be duplicated, so it
seems that it is not an isolated incident.  The following is a description
of the problem.

	The user has set default to a directory with the following protections
set on it:  SYSTEM:READ+WRITE+EXECUTE+DELETE, OWNER:RWED, G:RE, W:RE.  She
belongs to the same UIC group as the directory's owner.  She opens a file
JUNK.GEN in EMACS.  The file has the following protection set, SYSTEM:RWED,
OWNER:RWED, GROUP:RWED, WORLD: <no access>.  To open the file in EMACS she
types <ctrl>-x <ctrl>-f JUNK.GEN.  EMACS opens the file and puts her in
fundamental mode.  She makes a change to the file, EMACS notes the change
by putting a ** in the status line.  Using <ctrl>-x <ctrl>-s to save the
file, the user receives the following message from EMACS:

	IO error writing DISK$FLIGHT:[SIM.CMD]JUNK.GEN

Please note that with the above stated directory protection, I would expect
her to get this error.  Unfortunately, the file JUNK.GEN has been trashed.
Originally the file had 69 blocks of data residing in it.  Now the file has
none (it is empty).  How does EMACS bypass the directory protection?  It
shouldn't have done anything to the file at all?  Your assistance in this
matter will be most appreciated.

	David Guevara,
	Internet:  guevara@fsdvx2.arc.nasa.gov