Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think!snorkelwacker!bloom-beacon!bu.edu!bu-cs!xylogics!cloud9!lectroid!paris!lennox
From: lennox@paris.sw.stratus.com (Craig Scott Lennox)
Newsgroups: comp.sys.mac
Subject: Filenames, ARGH!!
Summary: Problems with writing a csh
Keywords: filenames, csh, spam
Message-ID: <591@lectroid.sw.stratus.com>
Date: 19 Jan 90 15:19:18 GMT
Sender: usenet@lectroid.sw.stratus.com
Reply-To: lennox@paris.sw.stratus.com (Craig Scott Lennox)
Organization: Stratus Computer, Software Engineering.
Lines: 18


I'm trying to write a csh for a Mac SE.  Say what you like, but there are some
times when you need to type commands rather than mouse them.

However, I'm stonewalled atthe beginning:  How can you write an effective
command interpreter when ANY character -- spaces, tabs, hyphens, underscores,
colons, etc. can be in your filenames.  Furthermore, with the limit on filename
length being 31-characters, that could make for some mighty hairy pathnames.

Are there any accepted or innovative ideas out there to overcome this hassle?  Any
information would be greatly appreciated (and given credit for!).


--

|    Craig Scott Lennox -- Stratus Computer - Marlborough,  MA     |
|           Dyslexic Existentialism:  "Is there a dog?"            |
| Find out what I really said -- send for your free decoder ring!  |