home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.wizards:4711 comp.unix.shell:4723 comp.unix.misc:4181
- Newsgroups: comp.unix.wizards,comp.unix.shell,comp.unix.misc
- Path: sparky!uunet!news.mtholyoke.edu!jbotz
- From: jbotz@mtholyoke.edu (Jurgen Botz)
- Subject: Re: The Problem with UNIX
- Message-ID: <Bxnu5E.KoH@mtholyoke.edu>
- Sender: news@mtholyoke.edu (USENET News System)
- Organization: Mount Holyoke College
- References: <aldavi01.721333614@starbase.spd.louisville.edu> <1992Nov11.194557.16258@yarc.uucp> <EEIDE.92Nov12120339@asylum.cs.utah.edu>
- Date: Fri, 13 Nov 1992 15:10:25 GMT
- Lines: 18
-
- In article <EEIDE.92Nov12120339@asylum.cs.utah.edu> eeide%asylum.cs.utah.edu@cs.utah.edu (Eric Eide) writes:
- >I know of somebody who is doing research in this direction: me. As part of my
- >Masters degree I am modifying the C shell to be more tolerant of errors, both
- >errors in syntax (e.g., typos) and semantics (e.g., inappropriate command line
- >arguments). My new shell keeps track of the user's command history in order to
- >make accurate corrections.
-
- Without wanting to make a judgement about the viability of the basic
- research underlying such a project, why are you starting with the C
- shell? If I wanted to create a user-interface that could deal with
- errors and ambiguities introduced by the user I would first make sure
- that the software itself isn't full of errors and ambiguities... i.e.,
- I sure as hell wouldn't use the C shell.
- --
- Jurgen Botz | Internet: JBotz@mtholyoke.edu
- Academic Systems Consultant | Bitnet: JBotz@mhc.bitnet
- Mount Holyoke College | Voice: (US) 413-538-2375 (daytime)
- South Hadley, MA, USA | Snail Mail: J. Botz, 01075-0629
-