csh, ksh, or sh?

[Azel The Destroyer]

>In article <3333 at ns-mx.uiowa.edu> wolf at piquet.cipl.uiowa.edu (Mike Wolf) writes:
>>We are in the process of determining what shell to use.  If I can get
>>the opinions, advice, and facts about problems with any of the
>>following shells:  csh, ksh, sh.

In article <1990Dec10.013209.29955 at cs.ucla.edu> gast at lanai.cs.ucla.edu 
(David Gast) writes:

>The ksh is far and above the best shell of these three.  If you have the
>$3K for a source license from AT&T go for it.  Make sure that you get the
>license for u of i and not just your group.

I don't know about that, as a user/programmer/semi-novice shell programmer I've
found sh to be the most lack-luster, ksh to be the most antagonistic, and
csh/tcsh to be the one I've felt the most comfortable with. Course that could 
just be a remenant of my C experience, and probably not the most objective 
statement around. 

There it is, if anyone cares.
--
_____________________________________________________________________________
		  ~			| Erik O'Shaughnessy
|\/\/\/|  	   ~			| Small Systems 
|      |  	 ~  	       		| New Mexico State University
|   *  |          ~ o==========		| Las Cruces, NM USA
| (x)(x)  	    	|_|====		| eoshough at dante.nmsu.edu
C      _) 		    ===		|------------------------------------
|  ,___|  		    ===		|"Do not follow the NULL pointer,
|    /    				| for that path leads to chaos, 
/____\    	Die Bart! Die!		| and madness." - me
|     \   				|
-----------------------------------------------------------------------------