Subject: Re: bin/10611: /usr/bin/which reads user's .chsrc even if user's shell is not csh
To: Todd Whitesel <email@example.com>
From: Robert Elz <kre@munnari.OZ.AU>
Date: 07/19/2000 21:36:32
Date: Wed, 19 Jul 2000 02:39:42 -0700 (PDT)
From: Todd Whitesel <firstname.lastname@example.org>
| IMHO not finding anything altered in the current shell is "arguably wrong".
That's certainly true - but not reading .cshrc doesn't fix that, it
goes the other way, and doesn't find aliases, etc, at all. The "arguably
wrong" in the earlier version of your man page revision concerned reading
cshrc, not whether which actually worked or not.
| As for flamage, if you don't care to hear the flames then it is better to
| refrain from posting your lighter fluid in the first place.
No, it isn't that I don't care to hear them, I don't care one way or
other - the ps was just to point out that just because I had said that
csh ought be trashed didn't mean it was going to happen - hence we don't
need to generate a large number of messages from people who haven't
discovered better shells yet and want csh retained. I think you can
just assume it will be retained - there's no need to demand that...
But if (as has been pointed out) csh has a builtin which now, then the
right thing to do with the which script is just to trash it - it doesn't work
for non csh users (who all have other builtin commands which do work)
and apparently isn't needed for csh users ... hence it is useful for no-one.