X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<416096c60912010803o33bf4c7dgbca2178307c83bcc@mail.gmail.com>
References:	<8d7f7110911300444l7ab3c2c8l5ac1edf0097d2065 AT mail DOT gmail DOT com> <4B142061 DOT 6000200 AT cygwin DOT com> <8d7f7110911301717jbafbc2ci432817b1c713f1e6 AT mail DOT gmail DOT com> <20091201013022 DOT GA2336 AT KCJs-Computer> <4B147423 DOT 1050404 AT bopp DOT net> <20091201153816 DOT GA21362 AT win DOT tue DOT nl> <416096c60912010803o33bf4c7dgbca2178307c83bcc AT mail DOT gmail DOT com>
From:	"DePriest, Jason R." <jrdepriest AT gmail DOT com>
Date:	Tue, 1 Dec 2009 12:42:01 -0600
Message-ID:	<31b7d2790912011042k625d8adak88022ead8be9633d@mail.gmail.com>
Subject:	Re: how to get the windows PATH env in cygwin
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Tue, Dec 1, 2009 at 10:03 AM, Andy Koppe <> wrote:
> 2009/12/1 Reinier Post:
>>> If you want to see the Windows PATH setting unmolested by Cygwin, you
>>> will either need to strip out the additions set by /etc/profile or avoid
>>> running under an environment modified by /etc/profile.
>>
>> It doesn't add, actually - it replaces it.
>
> You're wrong. The Cygwin DLL at startup translates the Windows PATH
> variable. And this line in /etc/profile adds to it:
>
> PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:$PATH
>
>

This is completely and totally true.

To verify it, all you have to do is open a bash prompt (Cygwin.bat,
mintty, rxvt, whatever) and then launch a cmd.exe or powershell.

Check the path in the bash prompt and you will see the cygwin stuff at
the beginning of it.

Check the path in the cmd.exe or powershell prompt which was run
*after* the bash script updated the path and you will see that it does
*not* include the cygwin paths.

It doesn't override what you have set anywhere but in cygwin's magic space.

-Jason

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

- Raw text -