You are not logged in. Login Now
 0-24   25-35         
 
Author Message
11 new of 35 responses total.
yecril71pl
response 25 of 35: Mark Unseen   Oct 8 16:44 UTC 2007

Neither do I --- but it would be obvious for POSIX to follow Bourne.
papa
response 26 of 35: Mark Unseen   Feb 14 00:14 UTC 2017

After tiring of the Grex menush, I decided to give tcsh a try for historic
interest (bash is my standard shell on Un*x systems where I have a choice).

I installed the tcshrc Project (https://sourceforge.net/projects/tcshrc/)
initialization files to give myself a head start. I found that the Project
assumes you're using a variety of Linux, so it took a little hacking to get
some of the features working on Grex's OpenBSD, which was both annoying and
fun.

I will not bother with tsch scripts beyond dabbling with the initialization
files. Within that range, although the syntax is different from the more
familiar Bourne-like shells, I have encountered no problems.

Overall, I like tcsh fine, with very little difference from bash for ordinary
use. I have not been able to get the incoming mail watch feature to work,
though I don't get much mail on Grex. tsch has a login watcher that I think
bash lacks which is interesting.

I guess that either tcsh or csh is or was the default shell on Grex because
the system-wide cshrc file looks like it's had quite a bit of customization.
kentn
response 27 of 35: Mark Unseen   Feb 15 01:52 UTC 2017

tcsh is my preferred shell and has been for a long time.  
papa
response 28 of 35: Mark Unseen   Feb 15 03:54 UTC 2017

Why do you prefer tcsh over something like bash? They seem
very similar to me.
kentn
response 29 of 35: Mark Unseen   Feb 16 02:52 UTC 2017

While they are similar, I like the vi command line in tcsh
much better than than in bash. I like all the features in
tcsh better. I don't do shell scripts in tcsh though.
papa
response 30 of 35: Mark Unseen   Feb 16 03:38 UTC 2017

I prefer Emacs key bindings for command line editingand
haven't noticed any problems with tcsh there.

I occasionally miss bash command syntax and redirection
options for longer complex commands. But it doesn't come
up often on Grex.
tod
response 31 of 35: Mark Unseen   Mar 14 17:28 UTC 2017

Long live bash and vi (though cash shell would make me happier)
papa
response 32 of 35: Mark Unseen   May 18 23:17 UTC 2017

I've been using tcsh (with the tcshrc package
https://sourceforge.net/projects/tcshrc/) since I came to Grex. It's not
bad, but the small differences with bash are becoming more annoying. I'm
thinking of switching back to bash.

tcsh can't find executables in the directory at the end of my $path list. Have
I missed some setting that will fix that?
papa
response 33 of 35: Mark Unseen   May 18 23:24 UTC 2017

I can't recreate the $path problem now. Never mind.
cross
response 34 of 35: Mark Unseen   May 19 00:21 UTC 2017

I used tcsh for nearly 20 years but switched away about a decade ago. Everyone
around me used bash, so I felt I should adapt instead of expecting the world
to accommodate me. Then I started using zsh most places.
cross
response 35 of 35: Mark Unseen   May 19 00:22 UTC 2017

Oh, PS: If you added or moved a command and experience that problem again,
try running `rehash`.
 0-24   25-35         
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss