X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.1 required=5.0 	tests=AWL,BAYES_20
X-Spam-Check-By: sourceware.org
Message-ID: <4E01B8FC54D24140A0EAF5118592D5BF@cit.wayne.edu>
From: "Lee Maschmeyer" <lee_maschmeyer AT wayne DOT edu>
To: <cygwin AT cygwin DOT 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> <31b7d2790912011042k625d8adak88022ead8be9633d AT mail DOT gmail DOT com>
Subject: Re: how to get the windows PATH env in cygwin
Date: Tue, 1 Dec 2009 15:24:45 -0500
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

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

Well, I just (gasp) tested! And awful lot of bandwidth wasting is being done 
by people who think they know how it works. But for me, at least, the path 
from the invocation of cmd was the same as the path in the Cygwin session 
from which it was invoked. Thus:

0/tty2W0(2)$ echo $PATH
/home/lmaschm/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c/Program 
Files/Common Files/Microsoft Shared/Windows Live:/c/WINDOWS
/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/WINDOWS/system32/WindowsPowerShell/v1.0:/c/Program 
Files/Common Files/Microsoft Sha
red/Windows Live:/usr/lib/lapack
0/tty2W0(2)$ cmd
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\cygwin-1.7\home\lmaschm>path
path
PATH=C:\cygwin-1.7\home\lmaschm\bin;C:\cygwin-1.7\usr\local\bin;C:\cygwin-1.7\bin;C:\cygwin-1.7\bin;C:\cygwin-1.7\usr\X11R6\bin;C:\P
rogram Files\Common Files\Microsoft Shared\Windows 
Live;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\
WindowsPowerShell\v1.0;C:\Program Files\Common Files\Microsoft 
Shared\Windows Live;C:\cygwin-1.7\lib\lapack

C:\cygwin-1.7\home\lmaschm>exit
exit
0/tty2W0(2)$


-- 

Lee Maschmeyer
Wayne State University
Detroit, Michigan, USA


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