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:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: can not find valid cygwin path
Date:	Tue, 1 Nov 2005 17:57:39 -0000
MIME-Version:	1.0
In-Reply-To:	<BAY105-F1956DF14E964FE23F3D9EBE96F0@phx.gbl>
Message-ID:	<SERRANOLpgTFur2iz2M0000007d@SERRANO.CAM.ARTIMI.COM>

lin q wrote:
>> From: "Dave Korn" <dave DOT korn AT artimiAAAARRRRGGGHHHHHH!>

  Oh no.  More spam.  :-(

  Please read http://cygwin.com/acronyms#PCYMTNQREAIYR!

> I do not quite get what you are saying and your example, I am using BASH
> which the default cygwin shell.

  Hmm, maybe I don't quite get what you are saying then!

> In your example you can see that "/cygdrive/c/prog/bin/nt" is the first
> element in $PATH, that is what we want; "$PROG_ENV/bin/nt/prog.exe" is
> expanded to "/cygdrive/c/prog/bin/nt/prog.exe" correctly.

  Yes, that is what I think is supposed to happen.

> These are all as expected, the problem is why the correct path can not be
> taken.
> 
> Do I miss anything? 

  Yes:  Why is _your_ example different from mine?  Look:
 
>>> export PROG_ENV=/cygdrive/c/prog
>>> export PATH=$PROG_ENV/bin/nt:$PATH
>>> 
>>> echo $PATH
>>> $PROG_ENV/bin/nt/prog.exe


  Here, PROG_ENV is *not* expanded.  So something has gone wrong, hasn't it?  


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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 -