cks@hawkwind.utcs.toronto.edu (Chris Siebenmann) (03/12/91)
Archive-name: unix/shell/ash/1991-03-09 Archive-directory: uunet.uu.net:/comp.sources.unix/volume19/ash/ [192.48.96.2] Original-posting-by: cks@hawkwind.utcs.toronto.edu (Chris Siebenmann) Original-subject: Re: echo question Reposted-by: emv@ox.com (Edward Vielmetti) tchrist@convex.COM (Tom Christiansen) writes: | From the keyboard of ramsey@NPIRS.Purdue.EDU (Ed Ramsey): | :Which shell, then? | One that's sh compatible. sh itself is pretty bare-bones, but still | better csh by a parsec or three. There's also the BRL shell, ksh, or | bash. There is also my personal favorite: ash, which can be found in volume 19 of your local comp.sources.unix archive site. Ash has shell functions (with arguments done right), the usual builtin commands, a simple but usefull form of command history, and it supports BSD job control (you need to make a small change to get it to support job control as a login shell). It's small, fast, and (IMHO) pretty damn nice; I've been using it as my login shell for more than a year now with no problems. If you want full command-line editing and suchlike, there's a sepperate general front end called 'atty' (it's also available in your local c.s.unix archives). -- "That way, it won't matter so much which architecture "wins" (except to MIPS and Moto), which was most definitely NOT the case in the 68k vx. x86 conflict. The 88k and the Rx000 both are CPUs that I can use without holding my nose." - Alan Lovejoy cks@hawkwind.utcs.toronto.edu ...!{utgpu,utzoo,watmath}!utgpu!cks