Date: Sun, 26 Aug 2001 15:31:22 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Kris Kennaway <kris@obsecurity.org>, Oliver Fromme <olli@secnetix.de>, freebsd-current@FreeBSD.ORG Subject: Re: Why is csh tcsh? This can be a bad thing... Message-ID: <20010826153121.A32124@xor.obsecurity.org> In-Reply-To: <3B8971BD.1E028F84@mindspring.com>; from tlambert2@mindspring.com on Sun, Aug 26, 2001 at 03:01:33PM -0700 References: <20010826015413.C92548@dragon.nuxi.com> <200108261120.NAA07025@lurza.secnetix.de> <20010826140236.A21698@xor.obsecurity.org> <3B8971BD.1E028F84@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 26, 2001 at 03:01:33PM -0700, Terry Lambert wrote: > Kris Kennaway wrote: > > On Sun, Aug 26, 2001 at 01:20:23PM +0200, Oliver Fromme wrote: > > > "Our" csh still behaves differently like any /bin/csh on > > > any other system that I know, and can't be easily made to > > > behave like them. > >=20 > > This is an assertion. Where is your supporting evidence? >=20 > Hit "TAB"? Controllable behaviour. Next? Kris P.S. It's already been established (and quite blindingly obvious) that tcsh has different defaults than csh, that's not the issue here. --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7iXi5Wry0BWjoQKURAhNSAJ411E0a4KY7HR7MC2DmN2lbzD9LKgCeN1ZY gBJzu0PARlud/CSjZhqYnHA= =zfl7 -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010826153121.A32124>