When comparing eltclsh vs tcsh, the Slant community recommends tcsh for most people. In the question“What are the best Bash replacements?” tcsh is ranked 10th while eltclsh is ranked 11th. The most important reason people chose tcsh is:
All the documentation that's needed to use tcsh is located in `man tcsh` instead of being spread on various helper programs.
Ranked in these QuestionsQuestion Ranking
TclVFS allows you access files inside ZIP archives or on remote HTTP and FTP servers like you would local files. If you put "package require vfs::urltype; vfs::urltype::Mount http"
in your ~/.eltclshrc you can do things like "file copy http://example.com/file /tmp/file" (HTTPS is currently not supported by TclVFS.)
Pro A more consistent alternative to the POSIX shell
Tcl is a saner scripting language built on the same principle as the Unix shell (everything is a string) with more than a hint of Lisp. eltclsh makes it possible to use Tcl interactively with tab completion for both language constructs and file paths. The result is that you can develop a snippet of Tcl code interactively and then paste it in your script.
Pro Organized documentation
All the documentation that's needed to use tcsh is located in
man tcsh instead of being spread on various helper programs.
Pro C-like shell
It's a C-like shell with tenex command-completion feature, which is very convenient.
eltclsh crashes on mismatched delimiters.
Con Limited support online
The support and number of guides and tutorials is rather limited for tcsh online because there are not many people who use it. At least compared to some of the other more popular alternatives.