This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: bash: setenv: command not found
- To: cabbey at bresnanlink dot net
- Subject: RE: bash: setenv: command not found
- From: Chet Ramey <chet at nike dot INS dot CWRU dot Edu>
- Date: Thu, 8 Feb 2001 07:47:27 -0500
- Cc: cygwin at cygwin dot com
- Read-Receipt-To: chet@po.CWRU.Edu
- Reply-To: chet at po dot CWRU dot Edu
> the answers to your question.
>
> setenv/unsetenv are commands that are built into the csh family
> of shells. Under bash the equivalent built ins are export and
> unset. For example:
>
> CSH: setenv name value
> BASH: export name=value
>
> CSH: unsetenv name
> BASH: unset name
>
> <soapbox>
> yes, this is a stupid naming convention, and it's one
> of the things I hate the most about shells... every one
> has a different version, and different syntax. There
> needs to be ONE standard, and I'm sorry to say BASH's
> answer isn't an answer; here csh got it right.
> </soapbox>
Why do you say that csh is right and bash is wrong?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)
Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple