Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 8 Feb 2001 12:37:49 -0500 From: Chet Ramey To: cabbey@bresnanlink.net Subject: RE: bash: setenv: command not found Cc: cygwin@cygwin.com, chet@po.cwru.edu Reply-To: chet@po.cwru.edu Message-ID: <1010208173749.AA50606.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 Thu, 8 Feb 2001 09:39:25 -0600 (CST) (id ) > 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@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple