Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!uwm.edu!uwvax!astroatc!nicmad!madnix!jason
From: jason@madnix.UUCP (Jason Blochowiak)
Newsgroups: comp.sys.apple2
Subject: Re: 5.0.2 Finder Bugs
Message-ID: <1239@madnix.UUCP>
Date: 6 Apr 90 00:13:41 GMT
References: <25fed47d.217d@polyslo.CalPoly.EDU> <1190@madnix.UUCP> <190@mstr.hgc.edu>
Reply-To: jason@madnix.UUCP (Jason Blochowiak)
Organization: ARP Software, Madison, WI
Lines: 43

In article <190@mstr.hgc.edu> mill7761@sa1.hgc.edu.UUCP (jeff miller) writes:
>In article <1190@madnix.UUCP> jason@madnix.UUCP (Jason Blochowiak) writes:
>> [Deleted part describing how to invoke the bug]
>>	Why this happens: The colon (':') is used to separate entries in a
>>pathname. So, ":RAM5:dir:file" describes the file "file" in the folder "dir"
>>on the volume ":RAM5", and ":RAM5:file" describes the file "file" on the
>>volume ":RAM5". 

>The name of a volume can not begin with a colon.
>Otherwise it is the name of a folder.  Perhaps this is the problem.

	Actually, a colon (':') cannot be part of a GS/OS filename, anywhere.
However, it can be used to separate folder names in a pathname, and is used
to begin a fully specified pathname. So ":RAM5" is the pathname that indicates
only the volume "RAM5". The colon isn't part of the name of the volume, but
it _is_ part of the pathname. The only times that full pathnames don't start
with a colon are 1) When you use one of the number prefixes (as in
"1:Something:Else"), or 2) When specifying a device name (as in ".MODEM").
You can use a partial pathname (as in "Something:Else"), but that simply
implies prefix 0 (so "Something:Else" is equivilent to "0:Something:Else").

	I just realized that, in my original post, I claimed that ":RAM5"
was a volume name... Whoops. Well, "RAM5" is the volume name that I meant to
mention. Reading back over the last 'graph, it seems like it's a moderately
decent explanation of the separator stuff, so I'll just leave it...

	Btw, that was just mis-explanation on my part (claiming that ":RAM5"
was the volume name) - the problem, as originally described, does exist, and
has nothing to do with the volume name.

	Seeing as I discovered this while attempting to copy a file on the
same volume (instead of moving it) - does anyone know how to copy a file on
the same volume without 1) Duplicating the file, 2) Moving the original
file, and 3) Renaming the duplicate? I tried holding down the option key,
but that didn't do what I wanted...

>Jeff


-- 
                      Jason Blochowiak - jason@madnix.UUCP
or, try:         astroatc!nicmad!madnix!jason@spool.cs.wisc.edu
       "Education, like neurosis, begins at home." - Milton R. Saperstein