--Hf61M2y+wYpnELGG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 30, 2006 at 02:53:23PM -0400, der Mouse wrote:
> > FWIW, I liked the idea suggesting to replace our /bin/csh with tcsh.
>=20
> Ugh!  Please, not unless it's a tcsh which has a csh-compatible mode
> (wherein, in particular, line editing is completely disabled, using
> plain read() to get command lines).  (I don't know whether any tcsh has
> such a mode; I avoid tcsh when I can.)

Note: I think there was a slight mis-parse in the original statement. I=20
don't think we'd make /bin/csh be /bin/tcsh. I think what we'd do is add=20
/bin/tcsh and make it the "default default" in place of /bin/csh.

I don't think anyone would actually support having tcsh install itself as=
=20
/bin/csh, for many reasons.

The default shell can also be changed, so regardless of what we make be=20
the "default default," an admin can select what s/he wants.

Take care,

Bill

--Hf61M2y+wYpnELGG
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFFIV4xWz+3JHUci9cRAk2RAJ93qPMA08YCkId0P99sbUvQErTbbQCfeWlm
b8j5LeFWLnlFxzRZ7ACXPIY=
=Hv9G
-----END PGP SIGNATURE-----

--Hf61M2y+wYpnELGG--