Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Thu, 8 Feb 2001 12:37:49 -0500
From:	Chet Ramey <chet AT nike DOT INS DOT CWRU DOT Edu>
To:	cabbey AT bresnanlink DOT net
Subject:	RE: bash: setenv: command not found
Cc:	cygwin AT cygwin DOT com, chet AT po DOT cwru DOT edu
Reply-To:	chet AT po DOT cwru DOT edu
Message-ID:	<1010208173749.AA50606.SM@nike.INS.CWRU.Edu>
Read-Receipt-To:	chet AT po DOT CWRU DOT Edu
MIME-Version:	1.0
X-In-Reply-To:	Message from cabbey AT bresnanlink DOT net of Thu, 8 Feb 2001 09:39:25 -0600 (CST) (id <Pine DOT LNX DOT 4 DOT 21 DOT 0102080923570 DOT 23798-100000 AT tweedle DOT cabbey DOT net>)

> call me crazy but I like orthogonality, and logically named
> commands.

You like two completely different ways of doing assignments?

First, export foo=bar is just convenient shorthand for

foo=bar
export foo

There is only one way to do assignment statements in sh: var=value.
All variable assignments are local, with the single exception of
variable assignments preceding a command.  `export' is the only way
to make a variable part of the environment.

sh-style shells are much more consistent.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)

Chet Ramey, CWRU    chet AT po DOT CWRU DOT Edu    http://cnswww.cns.cwru.edu/~chet/

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -