Path: utzoo!attcan!uunet!mcvax!ukc!tcdcs!csvax1!ecarroll From: ecarroll@csvax1.cs.tcd.ie (Eddy Carroll) Newsgroups: comp.sys.amiga Subject: Re: \ Message-ID: <45569@csvax1.cs.tcd.ie> Date: 24 May 89 10:26:35 GMT References: <31453@sri-unix.SRI.COM> Organization: Computer Science Department, Trinity College Dublin Lines: 33 In article <31453@sri-unix.SRI.COM>, paolucci@snll-arpagw.UUCP (Sam Paolucci) writes: > In article deven@rpi.edu (Deven Corzine) > writes: > ->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. Well, if you don't interpret things in quotes, how do you do something like "CON:0/0/640/200/CLI Window"? You need the quotes so you can include spaces in the window title, but now you're saying that this should be treated as a normal file, relative to the current directory? You can't have it both ways! I think the present situation is fine. I'm still curious as to how the original poster got a colon in the filename though - I've tried various combinations using the device name with no success. On the subject of devices, is anyone working on a ZOO: device which would let you CD to a Zoo Archive, DIR the contents and then read or execute various files within it just as if they were uncompressed. Writing wouldn't need to be implemented, only retrieval. I'd find this really useful. Of course, you'd need to allow colons to appear more than once in a device name for this to work (DIR ZOO:DF0:FRED.ZOO) :-) Eddy -- Eddy Carroll ----* Genuine MUD Wizard | "You haven't lived until INTER: ecarroll@cs.tcd.ie | until you've died in UUCP: {..uunet}!mcvax!ukc!cs.tcd.ie!csvax1!ecarroll | MUD!" - Richard Bartle