A few notes about the C shell. It is a
command line interpreter with
C-like syntax that has been a standard part of the
Unix operating system since the late 70s.
You don't spell the name of Unix programs in all caps. Use /bin/csh or csh.
Plain csh doesn't have extensive interactive command line editing facilities, but it supports command line completion. It also has history substitution syntax, which can refer back to previously issued commands and specify modifications, even when interactive command line editing is not available - for example, when outpu goes to a line printer, still a common situation in the days when csh was written . This is probably what xunker's writeup refers to.
For interactive use, an extended and bugfixed version of csh, tcsh, is much preferrable. It has extensive command line editing and completion facilities. Similar facilities are available nowadays in the bash and zsh shells.
To pit csh against bash as the programmer's tool of choice is a grave mistake, because it is to programmers that csh reveals its fundamental weaknesses and inferiority to /bin/sh derivatives, of which bash is one. The use of csh for scripting purposes is mostly the result of ignorance and is considered harmful by more experienced users.
This ignorance can be explained by the circumstance that /bin/csh is still the default shell on many Unix systems, especially the commercial and security aware ones. While bash, tcsh and zsh are much more convenient for interactive use, they also represent feature-bloated, untrusted third-party code, and many Unix systems don't provide them for that reason. This leaves csh as the best shell for interactive use, if your other choice is /bin/sh.