Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!pasteur!ucbvax!cbosgd!osu-cis!tut!lvc
From: lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani)
Newsgroups: comp.unix.questions
Subject: Re: C shell script files
Message-ID: <4795@tut.cis.ohio-state.edu>
Date: 19 Jan 88 13:34:03 GMT
References: <65200004@convexe> <448@taux01.UUCP>
Organization: The Ohio State University Dept of Computer and Information Science
Lines: 16

In article <448@taux01.UUCP> amos%taux01@nsc.com (Amos Shapir) writes:
>Better forget it! Use csh for interactive work, sh (or ksh) for command
>files. The command interface of csh is horrible: you can't nest if's and
>while's, keywords must be first on their line, you can't freely interchange
>semicolons with new-lines, you can't pipe the output of while's, etc, etc.

You are right that ksh is better than csh for command files, but it is
also excellent for interactive work.  I even think it is superior to csh
for interactive work.  The only thing that ksh can't do that csh can
(that I care about) is for aliases to manipulate their arguments.  Even
this can be gotten around by combining the alias with a function.  What
is csh so good at?
-- 
Larry Cipriani, AT&T Networks Systems (by day) Ohio State University (by night)
Domain: lvc@tut.cis.ohio-state.edu
Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (yes its right)