Re: Hypercard Question

[nathan@cco.caltech.edu (Nathan Mates)]

In article <3mctsa$krs@tuba.cit.cornell.edu>,
Jay Krell <jmk3@crux4.cit.cornell.edu> wrote:
>nathan@cco.caltech.edu (Nathan Mates) writes:

>>cd "Bad filename with spaces in it!!!"
>>get "Mac Luser filenames stink, don't they?"

>Yeah, almost as bad as Unix filenames. :)

>I think both Mac and Unix allow _everything_ except Mac's disallow
>colons and Unix disallows slashes and nuls. And Unix names can
>be, what, 256? chars while Macs are limited to 31.

   Yes, but we keep it under control. Because we have to quote
everything that's got weird names, and such names are a real hassle
anyhow, we limit outselves, and behave sanely. Mac users have no
hassle from putting every character they want in the filename, and
they don't think twice.

   Thus, unix names tend to be much nicer for those of us on text
terminals around the world (MS-DOG 8+3 sufferers can go flame Bill
Gates for not getting a clue until this 'Windoze 95' kludge), while
those who created the files don't think twice about the pain they
inflict on the rest of us.

Nathan Mates

P.S. If there isn't enough flamebait above, I'll just make a slide
comment about all the hunters with M16s doing far less harm to others
than all the street muggers with knifes. :P
-- 
<*> Nathan Mates http://www.ugcs.caltech.edu/~nathan/      <*>
# And he said to them, "To you has been given the secret of the
# Kingdom of God, but for those outside, everything comes in 
# parables" Mark 4:11, NRSV