Date: Thu, 11 Nov 2004 21:59:23 +0000 From: Kris Kennaway <kris@FreeBSD.org> To: Kevin Lyons <klyons@corserv.corserv.com> Cc: freebsd-hackers@freebsd.org Subject: Re: tcsh is not csh Message-ID: <20041111215923.GE582@hub.freebsd.org> In-Reply-To: <200411112237.iABMb6YV001471@corserv.corserv.com> References: <200411112237.iABMb6YV001471@corserv.corserv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 11, 2004 at 04:37:06PM -0600, Kevin Lyons wrote:
> 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]
Please raise tcsh compatibility bugs with the tcsh developers.
> ------
> 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.
Try to relax, it's only a shell and not worth this level of emotion.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041111215923.GE582>