Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Date: Thu, 8 Feb 2001 07:47:27 -0500
From: Chet Ramey <chet@nike.INS.CWRU.Edu>
To: cabbey@bresnanlink.net
Subject: RE: bash: setenv: command not found
Cc: cygwin@cygwin.com
Reply-To: chet@po.CWRU.Edu
Message-ID: <1010208124727.AA47875.SM@nike.INS.CWRU.Edu>
Read-Receipt-To: chet@po.CWRU.Edu
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-In-Reply-To:  Message from cabbey@bresnanlink.net of Wed, 7 Feb 2001 22:42:58 -0600 (CST) (id <Pine.LNX.4.21.0102072236010.22103-100000@tweedle.cabbey.net>)

> 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