Path: utzoo!attcan!uunet!lll-winken!snll-arpagw!paolucci From: paolucci@snll-arpagw.UUCP (Sam Paolucci) Newsgroups: comp.sys.amiga Subject: Re: ":" in file names Message-ID: <115@snll-arpagw.UUCP> Date: 18 May 89 00:46:23 GMT References: <110@snll-arpagw.UUCP> <1989May11.221814.10870@ziebmef.uucp> Reply-To: paolucci@snll-arpagw.UUCP (Sam Paolucci) Organization: Sandia National Labs, Livermore, CA Lines: 25 In article deven@rpi.edu (Deven Corzine) writes: ->In article <1989May11.221814.10870@ziebmef.uucp> mcp@ziebmef.uucp (Marc Plumb) writes: -> -> Make sure you specify a volume name, e.g. "df1:some/dir/the:file". -> Dos always looks for the first colon and uses that as a device -> name, but it's not smart enough to notice the second. -> ->"not smart enough"? I'd say that's the proper behavior. -> -> BTW, any opinions on what is The Right Thing to do with :'s in file names? -> If they should be disallowed, who should check and what should be done? -> ->Certainly. Allow colons in filenames. So you just have to specify a ->full pathname is all. Besides, disallowing colons in filenames would ->make it difficult for such devices as PATH:... Why should you have to specify the full pathname if the file name with the colon is within double quotes. It seems to me that anything within double quotes should not be interpreted. Unfortunately, that's not what happens. -- -+= SAM =+- "the best things in life are free" ARPA: paolucci@snll-arpagw.llnl.gov