Date: Tue, 22 Oct 1996 08:21:42 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Leath Muller <leathm AT gbrmpa DOT gov DOT au>
Cc: djgpp AT delorie DOT com
Subject: Re: HK: v 2.1
In-Reply-To: <326C15C2.3E7@gbrmpa.gov.au>
Message-Id: <Pine.SUN.3.91.961022081452.2800M-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 22 Oct 1996, Leath Muller wrote:

> My understanding was the Win95 simply looked at the long filenames when
> doing all its file I/O. It places the 8.3 format in the left half of
> the file description for DOS people who are used to seeing it there,
> and all the file descriptions that it uses on the right hand side of
> the dir listing. I have only ever seen DOS (ie, when booting straight
> into DOS or rebooting to DOS) put the ~ in the filename when:
> 	i)  There are two copies of a file with the same filename (8.3)
> 	ii) The filename is longer than 8 characters
> Does this make sense?

Since Windows 95 doesn't allow for any two files to have the same 8+3 
alias, it *must* change the 8+3 short name whenever the long one 
changes, or create a new 8+3 alias when I open a file with the old name 
after renaming it.  Windows does neither; that's a bug.

Consider this example:

 touch Makefile
		This creates a file with long name `Makefile' and short
		name `MAKEFILE'; so far so good.

 ren Makefile Makefile~
		This renames it to `Makefile~', but the short name stays
		`MAKEFILE'.  This is a bug IMHO.

 touch Makefile
		This touches `Makefile~', because it has the same short
		name as `Makefile', whereas you would expect it to create
		a new file called `Makefile'.  End of bug.

> If my previous paragraph is true and Win95 only looks at the long
> filename, then both edit and emacs would appear to behave correctly.

Emacs only works correctly when built with DJGPP v2.01; in v2.0, you get 
your edited text in Makefile~ and no backup file!