Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!samsung!uunet!snorkelwacker!ai-lab!zurich.ai.mit.edu!cph
From: cph@zurich.ai.mit.edu (Chris Hanson)
Newsgroups: comp.sys.hp
Subject: Re: Availability of tcsh for HP-UX? Please, respond!
Message-ID: <CPH.90Aug9133639@kleph.ai.mit.edu>
Date: 9 Aug 90 17:36:39 GMT
References: <OJU.90Aug2101956@elektra.hut.fi> <5570463@hpfcdc.HP.COM>
Sender: news@wheaties.ai.mit.edu
Organization: M.I.T. Artificial Intelligence Lab.
Lines: 22
In-reply-to: donn@hpfcdc.HP.COM's message of 9 Aug 90 00:22:41 GMT

In article <5570463@hpfcdc.HP.COM> donn@hpfcdc.HP.COM (Donn Terry) writes:

   From: donn@hpfcdc.HP.COM (Donn Terry)
   Date: 9 Aug 90 00:22:41 GMT

   On the issue of choice of shell (and here I'm wearing my standards hat,
   not my HP hat) you probably are better off learning ksh than continuing
   to use (t)csh, because the POSIX.2 shell is something halfway (more or
   less) between ksh and sh.  It uses the sh syntax, and in POSIX.2a,
   has ksh editing.

   (I do miss the {} stuff, but it's really hard to do it right.)

   Donn Terry

An alternative that is available now is BASH, the GNU Bourne-Again
SHell.  It, like ksh, supports editing and job control.  But in
addition, BASH provides {} syntax like csh.  Best of all, you get the
source code with it.

BASH is available from "prep.ai.mit.edu" by anonymous ftp, in the
"pub/gnu/" directory.