X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 13 Oct 2010 01:36:46 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: nodosfilewarning not working Message-ID: <20101013053646.GA15747@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <29948673.post@talk.nabble.com> <20101013011127.GA14097@ednor.casa.cgf.cx> <29948823.post@talk.nabble.com> <20101013014122.GA14285@ednor.casa.cgf.cx> <29948971.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29948971.post@talk.nabble.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, Oct 12, 2010 at 06:59:26PM -0700, Autotoonz wrote: >I just tried running the batch file directly (as a per the commands >listed above), and the warning is now suppressed. Because I was >calling it from another batch file, the env variable was of course >lost. So my mistake here, although this is an easy trap to fall into >for the unaware! If you mean that batch file 1 sets the CYGWIN environment variable and then directly runs batch file 2, then that works too. That's how environment variables work - once you set an environment variable it is inherited by all subsequent processes unless the process goes out of its way to reset it. If you mean batch file 1 sets an environment variable and then, in another window, you run batch file 2, then that will not have the desired effect. cgf -- 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