Csh, Bash, and Ksh----a lesson of blood and tear

On Jun 23rd, 2009. I am working on a linux box. I find, constantly a lot of commands doesn't work, like what I usually did, vi, export, java. and I checked the path, the path is not seperated by :

 

when I echo $SHELL, I find it's Csh. I guess that's the root reason! This cost me 2 days time. I hate it.

 

Next time, when I use linux server, the first command I will issue is, ksh

 

Ksh use . ./set-env.sh to export all env in the sh into the current shell.

Csh use source ./set-env.sh to export all env in the sh into the current shell. (right?)

 

Ksh can use export command to see all current exported env variables. Csh can't.