Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	ericblake AT comcast DOT net (Eric Blake)
To:	Reid Thompson <Reid DOT Thompson AT ateb DOT com>,
	Ross MacGillivray <ross_macgillivray AT yahoo DOT ca>, cygwin AT cygwin DOT com
Subject:	RE: Path Statement Not Being Evaluated by Bash in Cygwin
Date:	Tue, 05 Jul 2005 20:34:20 +0000
Message-Id:	<070520052034.8284.42CAEECC000BFC380000205C22064244130A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender:	ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> > when I start bash and enter 'echo $path'.  This is the path statement
> > returned. 
> 
> Not sure how you've got things setup, but `echo $path`  should result in
> an empty return statement.  the variable is PATH not path, case
> sensitive.  
> 

Or maybe you are thinking of  tcsh syntax, where $path is a
space-separated synonym for the colon-separated $PATH.  tcsh
syntax doesn't work in bash (hopefully, it is obvious why not),
and your listing had colons, so even if you were to use tcsh with
that $path you would have problems.

--
Eric Blake
cygwin bash maintainer



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -