Subject: Re: pkgsrc and tcsh
To: None <andrew@grillet98.freeserve.co.uk>
From: Lubomir Sedlacik <salo@Xtrmntr.org>
List: port-sparc
Date: 05/28/2002 11:22:50
--E13BgyNx05feLLmH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 28, 2002 at 10:18:56AM +0100, Andrew Grillet wrote:
> So would I, In fact, I'd like tcsh to be considered for inclusion as
> part of the core system. Lets face it, as a user interface, it is far
> better than csh, and if your system has a problem, you probably want
> to use tcsh to fix it rather than csh. Be honest, command line editing
> and filename compeletion ARE good ideas, and "cos they had not been
> invented in 1978" is not a good reason for not using them. However, I
> also agree that its right not to pretend tchs is csh without the
> decison being taken by the sysadmin.

so use /bin/ksh, then.  it has command line editing and filename
completion, even history and other bells and whistles.  and it's part of
the base system.

regards,

--=20
-- Lubomir Sedlacik <salo@Xtrmntr.org>   ASCII Ribbon campaign against  /"\=
 --
--                  <salo@silcnet.org>   e-mail in gratuitous HTML and  \ /=
 --
--                                       Microsoft proprietary formats   X =
 --
-- PGPkey: http://Xtrmntr.org/salo.pgp                                  / \=
 --
-- Key Fingerprint: DBEC 8BEC 9A90 ECEC 0FEF  716E 59CE B70B 7E3B 70E2     =
 --

--E13BgyNx05feLLmH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (NetBSD)

iD8DBQE880xpWc63C347cOIRAtUIAKCbaWlauASd0mE1Mjy6qiubBEsJegCgs7rq
z0McTXoOy6Njef1Ibgq1hZQ=
=7fP/
-----END PGP SIGNATURE-----

--E13BgyNx05feLLmH--