From owner-freebsd-questions Tue Jul 18 16:30:11 2000 Delivered-To: freebsd-questions@freebsd.org Received: from odin.acuson.com (odin.acuson.com [157.226.230.71]) by hub.freebsd.org (Postfix) with ESMTP id 7791A37B5B3 for ; Tue, 18 Jul 2000 16:30:08 -0700 (PDT) (envelope-from djohnson@acuson.com) Received: from acuson.com ([157.226.69.47]) by odin.acuson.com (Netscape Messaging Server 3.54) with ESMTP id AAA61C5; Tue, 18 Jul 2000 16:32:03 -0700 Message-ID: <3974E7F5.1A02E214@acuson.com> Date: Tue, 18 Jul 2000 16:27:49 -0700 From: David Johnson Organization: Acuson X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.5.1 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: "David J. Kanter" Cc: FreeBSD questions Subject: Re: Bad Shells and the People Who Love Them... References: <20000718175345.A95605@localhost.localdomain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David J. Kanter" wrote: > > I'd like to learn a shell fairly well and chose csh because it's in the base > FreeBSD system (a little graybeard character) and I found good documentation > on it written by William Joy. But I've read some things that it's a "bad" > shell. If you are not writing shell scripts, or if they all will be quick and dirty five-liners, then it really doesn't matter what shell you use as long as you like it. But when you start writing real scripts, stick to vanilla sh or csh (not bash or tcsh) for your user scripts, and stick with just sh for system scripts. This doesn't mean to throw out bash or tcsh (well okay, you can throw out bash :-) ), but just make sure that any scripts you write follow the sh or csh subsets. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message