wolf@piquet.cipl.uiowa.edu (Mike Wolf) (11/29/90)
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. Known bugs, inadequacies, etc. is what I'm hoping for. Thanks to all who will lend their words. Michael Reply to: wolf@mel.cipl.uiowa.edu Disclaimer? Hell, I dont' even know her!
gast@lanai.cs.ucla.edu (David Gast) (12/10/90)
In article <3333@ns-mx.uiowa.edu> wolf@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. 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. David
longshot@harbor.ecn.purdue.edu (Longshot (tm)) (12/10/90)
In article <1990Dec10.013209.29955@cs.ucla.edu> gast@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. Does anyone know if there is a PD ksh? If so, where can I find it? -- longshot@ecn.purdue.edu (Rich Long) To be "remembered with an affection and veneration that shall surge high above the waters of oblivion and glisten through the rust of time."
eoshough@nmsu.edu (Azel The Destroyer) (12/11/90)
>In article <3333@ns-mx.uiowa.edu> wolf@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@cs.ucla.edu> gast@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@dante.nmsu.edu C _) === |------------------------------------ | ,___| === |"Do not follow the NULL pointer, | / | for that path leads to chaos, /____\ Die Bart! Die! | and madness." - me | \ | -----------------------------------------------------------------------------
carroll@cs.uiuc.edu (Alan M. Carroll) (12/11/90)
In article <EOSHOUGH.90Dec10090912@dante.nmsu.edu>, eoshough@nmsu.edu (Azel The Destroyer) writes: > > >In article <3333@ns-mx.uiowa.edu> wolf@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@cs.ucla.edu> gast@lanai.cs.ucla.edu > (David Gast) writes: > > >The ksh is far and above the best shell of these three. This is certainly my opinion. I've extensively customized my Korn Shell environment, and developed small and medium sized applications in Korn Shell. It is the best as a shell, and as a programming language. -- Alan M. Carroll "It's psychosomatic. You need a lobotomy. Epoch Development Team I'll get a saw." CS Grad / U of Ill @ Urbana ...{ucbvax,pur-ee,convex}!cs.uiuc.edu!carroll
tchrist@convex.COM (Tom Christiansen) (12/11/90)
In article <1990Dec10.193740.19406@ux1.cso.uiuc.edu> carroll@cs.uiuc.edu (Alan M. Carroll) writes: >> >The ksh is far and above the best shell of these three. >This is certainly my opinion. I've extensively customized my Korn >Shell environment, and developed small and medium sized applications >in Korn Shell. It is the best as a shell, and as a programming >language. Well, there's some debate about whether you want to use a shell as a programming language for anything more than very simple command scripts. For small applications, maybe in some cases it's ok; certainly ksh is better at this than csh, which is a joke for programming. For medium-sized tasks, and some kinds of small ones too, I'll take perl over any mere command shell any day. You will find that tcsh offers some nice features that ksh lacks, including asynch notification of change in job status (even csh gives you that), spelling correction, and expression history (again, csh does that too), curly brace expansion (csh has this) and rebinding of editing keys and quite a bit of other fluff. Ksh does have a more realistic vi mode than tcsh. The bash shell from GNU tries to address many of the problems that ksh has, being somewhat the logical and aesthetically pleasing union of ksh and tcsh. It does use sh syntax, not csh; this is by many considered a feature. When I tried it a year ago, it was still a bit buggy, but a lot of work has been done on it since then. It's also free, unlike any of the aforementioned shells (tcsh diffs to csh are free, but csh itself is not.) In summary, you don't really ever want sh or csh for much of anything. For interactive work, I'd look at ksh and tcsh, or better yet bash. For programming, sh actually is more portable than the others, but you can do very little of any complexity (without pain and suffering) if you limit yourself to its capabilities. If you want much more complexity than sh gives you, abandon shells all together and look at perl. This is, of course, merely my own opinion; you should try to form your own. It's certainly taken me many years to form mine; you deserve the same chance. --tom -- Tom Christiansen tchrist@convex.com convex!tchrist "With a kernel dive, all things are possible, but it sure makes it hard to look at yourself in the mirror the next morning." -me