From owner-freebsd-chat Sat Apr 15 15:30:56 2000 Delivered-To: freebsd-chat@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 9D03C37B55B for ; Sat, 15 Apr 2000 15:30:42 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA04998 for freebsd-chat@freebsd.org; Sun, 16 Apr 2000 00:30:41 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id AAA58076 for freebsd-chat@freebsd.org; Sun, 16 Apr 2000 00:05:18 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: cvs commit: src/contrib/tcsh - Imported sources Date: 16 Apr 2000 00:05:17 +0200 Message-ID: <8dap2t$1ome$1@bigeye.rhein-neckar.de> References: <200004150441.VAA23755@freefall.freebsd.org> To: freebsd-chat@freebsd.org Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David E. O'Brien wrote: > Import the latest version of the 44BSD C-shell -- tcsh-6.09. I'm unhappy about this for a reason that hasn't even been mentioned in the monster thread that clogged -arch: Including tcsh in the base system means that people will use it. csh clearly isn't good enough for people to use, and when they looked around for a better interactive shell, many found their way to proper sh-ish shell like bash or ksh. Now they will stay with tcsh instead. And they will write (t)csh scripts. Importing tcsh gives new life to a shell family that should die, die, die. From a shell advocacy point of view, importing tcsh was the very worst thing that could happen. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message