home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.wizards:4809 comp.unix.shell:4803
- Path: sparky!uunet!sun-barr!cs.utexas.edu!usc!sdd.hp.com!spool.mu.edu!olivea!charnel!sifon!thunder.mcrcim.mcgill.edu!mouse
- From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
- Newsgroups: comp.unix.wizards,comp.unix.shell
- Subject: Re: The Problem with UNIX
- Message-ID: <1992Nov20.092623.19870@thunder.mcrcim.mcgill.edu>
- Date: 20 Nov 92 09:26:23 GMT
- References: <1992Nov9.172715.16367@cs.wisc.edu> <1992Nov11.194557.16258@yarc.uucp> <id.2X1V.U99@ferranti.com>
- Organization: McGill Research Centre for Intelligent Machines
- Lines: 25
-
- In article <id.2X1V.U99@ferranti.com>, peter@ferranti.com (peter da silva) writes:
- > In article <1992Nov13.091914.6799@thunder.mcrcim.mcgill.edu> mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes:
-
- >> Yes, it might. So what? Is "acceptance in the general
- >> microcomputer market place" something we wish for UNIX?
- > If we want to keep being able to buy nice cheap UNIX systems with
- > decent performance for the long-term, yes.
-
- Keep? You mean they're available now? The only decent systems I know
- of are ones you have to put together from pieces yourself anyway....
-
- > I would say that a friendly shell that does all the command parsing
- > (like DCL does) would be quite a nice touch.
-
- You need the equivalent of .cld files to do this. Since *nobody*
- provides them, your user has to write them for every new program
- obtained - and that kinda defeats the purpose of having them to begin
- with.
-
- (I *think* .cld is the right extension; it's been a long time.)
-
- der Mouse
-
- mouse@larry.mcrcim.mcgill.edu
-