home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.apple2.gno
- Path: sparky!uunet!paladin.american.edu!gatech!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!ee.ualberta.ca!jpenne
- From: jpenne@ee.ualberta.ca (Jerry Penner)
- Subject: Re: Why csh? (Re: unshar needed & sh dis...)
- Message-ID: <jpenne.725421000@ee.ualberta.ca>
- Sender: news@kakwa.ucs.ualberta.ca
- Nntp-Posting-Host: eigen.ee.ualberta.ca
- Organization: University Of Alberta, Edmonton Canada
- References: <behrenss.724869178@hphalle6> <1992Dec21.160930.1472@r-node.gts.org> <1h5c80INN9ba@charnel.ecst.csuchico.edu> <1992Dec22.120955.13131@quando.quantum.de> <bazyar.725048507@teal> <jpenne.725237760@ee.ualberta.ca> <bazyar.725291247@teal>
- Date: Sun, 27 Dec 1992 01:50:00 GMT
- Lines: 27
-
- bazyar@teal.csn.org (Jawaid Bazyar) writes:
-
- > gsh takes a lot of inspiration from tcsh, the modern derivative of
- >csh, which provides command-line editing, smarter path handling,
- >and filename and command completion.
-
- Good.
-
- > We never studied a whole lot on any aspect of why csh's script
- >language might be considered 'broken'. Can you provide some examples?
-
- I can only think of one off the top of my head, but csh has a bug when
- you type 'if ( expression...' and you forget the spaces around the (.
- There are others. I basically quit using 'csh' when I ran into stuff
- like this and forgot about its problems. Since you guys didn't port
- csh you won't have run into these types of problems.
-
- > gsh is completely (100%) decoupled from the kernel. We did it just
- >like Unix because, well, Unix did it right :) chsh .. is trivial,
- >but right now gsh is the only shell we've got. I expect this to
- >change in the future. gsh also provides some IIgs-specific
- >support that the Unix based shells cannot (like AppleWorks _and_ emacs
- >style command line editing).
-
- Sounds good.
- --
- Jerry Penner jpenne@ee.ualberta.ca Try a 1-line .sig today.
-