From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 11 21:33:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3712516A4CE for ; Thu, 11 Nov 2004 21:33:42 +0000 (GMT) Received: from corserv.corserv.com (tx-65-40-201-169.sta.sprint-hsd.net [65.40.201.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id A253543D54 for ; Thu, 11 Nov 2004 21:33:41 +0000 (GMT) (envelope-from klyons@corserv.corserv.com) Received: (from klyons@localhost) by corserv.corserv.com (8.12.11/8.11.6) id iABMb6YV001471 for freebsd-hackers@freebsd.org; Thu, 11 Nov 2004 16:37:06 -0600 (CST) (envelope-from klyons) Date: Thu, 11 Nov 2004 16:37:06 -0600 (CST) From: Kevin Lyons Message-Id: <200411112237.iABMb6YV001471@corserv.corserv.com> To: freebsd-hackers@freebsd.org Subject: tcsh is not csh X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 21:33:42 -0000 I have (re)discovered that tcsh is not csh although the tcsh man page falsely asserts backward compatibility. Trying to do a simple read of multiword variables in tcsh fails yet works find on csh. The tcsh man page admits as much when one gets to the $< part. The point is, csh should be the basic backward compatibly lowest common denominator between systems. This is a real problem. I humbly suggest that those that want the bang of tcsh can do a pkg_add just like the morons that want bash instead of sh. If you want to try an example, do the following on csh, and then on tcsh. #!/bin/csh echo enter some words set line = $< set words = ($line) echo line is $line echo word1 is $word[1] echo word2 is $word[2] echo word3 is $word[3] ------ The fact that tcsh can not do this in default mode is beyond pathetic. What is worse is that freebsd didn't notice or care. .