wow. or maybe I mean s/wow/ow/

I didn't think 'we' did that any more.

csh scripts don't reflect on non-csh user initialization much. So if something
is in a /bin/sh /etc/profile or a sh/bash/ksh shell initialization space,
the which command won't 'find' it because it doesn't wind up in the path=(...)
space.

Hmm. This might be me needing cluebat attack. Should I be doing shell PATH
initialization in places which csh honours? What are they these days?

-George