Date: Wed, 13 Oct 2010 01:36:46 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: nodosfilewarning not working
Message-ID: <20101013053646.GA15747@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <29948673 DOT post AT talk DOT nabble DOT com> <20101013011127 DOT GA14097 AT ednor DOT casa DOT cgf DOT cx> <29948823 DOT post AT talk DOT nabble DOT com> <20101013014122 DOT GA14285 AT ednor DOT casa DOT cgf DOT cx> <29948971 DOT post AT talk DOT nabble DOT 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 AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT 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