On Fri, 2010-06-11 at 11:46 +0930, Malcolm Kay wrote:
On Fri, 11 Jun 2010 02:49 am, Dan D Niles wrote:
I had been using csh/tcsh for 20 years and I just switched to
bash. The recent discussion about the differences between the
shells prompted me to take another look at bash. I thought
I had been using csh/tcsh for 20 years and I just switched to bash. The
recent discussion about the differences between the shells prompted me
to take another look at bash. I thought I'd share my perception of the
differences between tcsh and bash.
The big thing tcsh is lacking, and the reason
Dan D Niles d...@more.net writes:
The which command functions differently between bash and tcsh. For
example, I have ls aliased to do color output and add some other options
that I like. With tcsh, 'which ls' returns
ls: aliased to \ls -GFB; with bash it returns
/bin/ls. The tcsh
In the last episode (Jun 10), Lowell Gilbert said:
Dan D Niles d...@more.net writes:
The which command functions differently between bash and tcsh. For
example, I have ls aliased to do color output and add some other options
that I like. With tcsh, 'which ls' returns
ls:
On Thu, 10 Jun 2010 13:41:32 -0400
Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org articulated:
bash (like most other sh-style shells) has no which builtin. You
end up running /usr/bin/which. bash (like most other sh-style
shells) does have a (rough) equivalent, which is type
On Fri, 11 Jun 2010 02:49 am, Dan D Niles wrote:
I had been using csh/tcsh for 20 years and I just switched to
bash. The recent discussion about the differences between the
shells prompted me to take another look at bash. I thought
I'd share my perception of the differences between tcsh and
