response 14 of 35:

Sep 21 00:30 UTC 2006

zsh, simple yet powerful. I've been using it ever since my slackware days.

response 16 of 35:

Sep 21 16:44 UTC 2006

No, neither have I.

response 18 of 35:

Sep 21 19:35 UTC 2006

Party of the problem with info pages is that they force a specific usage
model.  It works fine if you "live" within emacs and are used to that style,
but kind of sucks if you want to, say, pipe info through other things, etc.

response 20 of 35:

Mar 22 09:06 UTC 2007

I have been using bash for several years.  Before that I was a tcsh user
for several years because it was better than csh (a few years) by a lot,
and those two supported command aliasing while bash did not at that
time.  Once Bash got command aliasing (and I actually noticed it) I got
tired of making sure my environment had tcsh.

response 22 of 35:

Oct 7 14:34 UTC 2007

Sh and bash use $? for exit status.

response 24 of 35:

Oct 8 13:07 UTC 2007

I don't know the answer, and a little Google searching (which I imagine
you've tried too) didn't turn one up for me.  But since a suspended
command hasn't really "exited", I'm not sure I'd expect suspension to be
reflected in the value of an "exit status" variable anyway.

Does someone else know?

On a somewhat related matter, my searching did turn up a difference
between bash and tcsh in the semantics of the "&&" operator.  If you do

    echo one && sleep 20 && echo two

in bash, and then suspend the sleep with ctrl-z, "$?" is set to 0 and
"echo two" is executed immediately, even though the sleep hasn't exited.
 But if you execute the same sequence in tcsh and suspend with ctrl-z,
"$?" is set to 1 and "echo two" is *not* executed.

Hmmm...  I wonder what the correct POSIX behavior is.

response 26 of 35:

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.

response 28 of 35:

Feb 15 03:54 UTC 2017

Why do you prefer tcsh over something like bash? They seem
very similar to me.

response 30 of 35:

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.

response 32 of 35:

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?

response 34 of 35:

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.