Date: Thu, 6 Apr 2000 14:47:40 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: arch@freebsd.org Subject: Re: Import of tcsh into src/contrib/, replacing src/usr.bin/csh Message-ID: <20000406144740.B25177@dragon.nuxi.com> In-Reply-To: <200004062121.OAA90627@apollo.backplane.com>; from dillon@apollo.backplane.com on Thu, Apr 06, 2000 at 02:21:36PM -0700 References: <20000406134916.A23265@dragon.nuxi.com> <200004062121.OAA90627@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 06, 2000 at 02:21:36PM -0700, Matthew Dillon wrote: > I don't think we can replace /bin/csh with tcsh, for compatibility > reasons. Thousands upon thousands of scripts use csh and the risk > is just too great that we might break some of them. Show me one. > Remember /bin/sh vs /bin/bash? I'll admit /bin/csh vs /bin/tcsh is > less of a problem, but it's still a problem. Bash is a totally different code base then sh. tcsh is our BSD csh + enhancements. Where is the problem? > I would also propose that the default csh.cshrc (which tcsh sources) > still be used for both tcsh and csh since it's so trivial to test which > one is sourcing the file. I do *NOT* recommend creating a separate > .tcshrc. Agreed. > And I would also propose that we turn command-line partial-history- > completion on by default. Yes, one of the primary reasons for what I want to do. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000406144740.B25177>