X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4B15894C.9070708@gmail.com>
Date: Tue, 01 Dec 2009 21:23:24 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: how to get the windows PATH env in cygwin
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> <4E01B8FC54D24140A0EAF5118592D5BF AT cit DOT wayne DOT edu>
In-Reply-To: <4E01B8FC54D24140A0EAF5118592D5BF@cit.wayne.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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

Lee Maschmeyer wrote:
>> 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. 

  Even more bandwidth being wasted by people who misread the instructions.
When it says "Open a bash prompt and then launch a cmd.exe" it doesn't say you
are to launch it /from/ the bash prompt.  It means launch it *after* the bash
prompt in time.

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

  You weren't supposed to invoke it from the Cygwin session.  Of course, you
could point out that the original wording was ambiguous.  I noticed it was
ambiguous too, but rather than vainly assume the OP was stupid and I was
clever, I just worked out which one of the two possibilities the OP must have
intended based on the assumption that he was *not* stupid and since one of
those two possibilities produced exactly the results OP claimed they would it
was obvious which one OP was referring to.

  You would do well to reset your default assumptions about other people.

    cheers,
      DaveK

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