Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!ginosko!gem.mps.ohio-state.edu!csd4.csd.uwm.edu!uakari.primate.wisc.edu!nic.MR.NET!umn-cs!bungia!orbit!pnet51!dougm
From: dougm@pnet51.orb.mn.org (Doug Mcintyre)
Newsgroups: comp.sys.apple
Subject: space char in file names
Message-ID: <991@orbit.UUCP>
Date: 8 Sep 89 15:25:04 GMT
Sender: root@orbit.UUCP
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 34

stowekeller@pro-carolina.cts.com (Stowe Keller) writes:
>re: allowing lowercase-period = space chr in ProDOS filenames
> 
>        I can think of a good reason not to allow spaces in ProDOS filenames:
>it would screw up all the existing command line shells for ProDOS which use
>the space chr as a delimiter between multiple filenames, option switches, etc.
>
>                        Stowe
>
>------------------------------------------------------------------------
>Stowe Keller                            Author of ProDOS8 LIST utility
>CompuServe: 71540,725       GEnie: SKELLER       BIX: stowekeller
>UUCP: [ sdcsvax nosc ] !crash!pro-carolina!stowekeller
>ARPA: crash!pro-carolina!stowekeller@nosc.mil
>INET: stowekeller@pro-carolina.cts.com

I wrote a reply to the originaly poster with something like that.. You can do
it, but people would be confused with it.. Suppose you have three files with
the names..

one
two 
one two

And then you type 'compress one two'. This will compress files one and two, to
compress file one two, you'd have to type 'compress "one two"', and that would
probably confuse many a people. Especially since no other OS that works with a
command shell has spaces in files names (ie. messy-dos & Unix.. ) I could be
wrong about messy-dos, since I've never used it..


UUCP: {rosevax, crash}!orbit!pnet51!dougm                Compuserve: 70611,2215
ARPA: crash!orbit!pnet51!dougm@nosc.mil                        ALPE: DougMac
INET: dougm@pnet51.cts.com                                    GENIE: D.MCINTYRE1