From owner-freebsd-questions@FreeBSD.ORG Fri Dec 14 19:25:36 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F5A016A4A1 for ; Fri, 14 Dec 2007 19:25:36 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id 6FDAE13C442 for ; Fri, 14 Dec 2007 19:25:36 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 18958 invoked from network); 14 Dec 2007 19:25:36 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 14 Dec 2007 19:25:35 -0000 Message-ID: <4762D814.6000704@chuckr.org> Date: Fri, 14 Dec 2007 14:23:00 -0500 From: Chuck Robey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.9) Gecko/20071107 SeaMonkey/1.1.6 MIME-Version: 1.0 To: Jerry McAllister References: <20071214010542.GA19553@demeter.hydra> <200712132012.32729.mike.jeays@rogers.com> <20071214011614.GA18559@gizmo.acns.msu.edu> In-Reply-To: <20071214011614.GA18559@gizmo.acns.msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Jeays , FreeBSD Questions Subject: Re: Apparently, csh programming is considered harmful. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Dec 2007 19:25:36 -0000 Jerry McAllister wrote: > On Thu, Dec 13, 2007 at 08:12:32PM -0500, Mike Jeays wrote: > >> On December 13, 2007 08:05:42 pm Chad Perrin wrote: >>> I ran across this today: >>> >>> http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/ >>> >>> Title: >>> Csh Programming Considered Harmful >>> >>> I wonder what responses I might get here, and how much of this applies to >>> tcsh as well (I'm still not exactly a tcsh expert). >> As you can see, it is 11 years old, but still good advice. For interactive >> use, tcsh is not too bad, but for writing scripts of any length, sh or bash >> are considered better tools. For code that will run anywhere, stick to the >> sh subset. >> >> Bash has all the features one is likely to need for interactive use >> as well, and one could make a good case for it being the 'standard' shell >> now. > > Here it is. > I find bash to be ugly and hate it for interactive use. > I would rather just use /bin/sh. As long as folks don't stop me from running whatever I want, I don't care if you use bash, but it really irks me, that most Linux systems are broken in that respect: Most of them break badly in random ways, if you don't run bash as your shell. That's poor programming practice, but the Linux programmers, since they all run bash themselves, they don't see the results of their errors, and they all claim its not a problem. Try running tcsh there, you'll see what I mean reasonably soon, when you begin to get random weirdnesses...