Message-ID: <4CB5591A.4000901@veritech.com>
Date: Wed, 13 Oct 2010 03:00:42 -0400
From: "Lee D. Rothstein" <l1ee057@veritech.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: "Cygwin, eMail List" <cygwin@cygwin.com>
Subject: Re: nodosfilewarning not working
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> <20101013053646.GA15747@ednor.casa.cgf.cx> <29949816.post@talk.nabble.com>
In-Reply-To: <29949816.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

  On 10/13/2010 1:58 AM, Autotoonz wrote:
> Christopher Faylor-8 wrote:
>> 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.
> Yeah that's what I meant - batch file 1 sets env variable and then calls
> batch file 2.
> And you are correct - env variables set in the parent DOS process are
> inherited by child DOS processes.
> So now I'm stumped as to what caused my original problem, because I spent
> about one hour checking and re-checking that my DOS set command was correct
> (ie: set CYGWIN=nodosfilewarning) and then googling for clues.
> Unfortunately I cannot repeat the fault, so I'm going to have to put this
> down to a typo on my part. If I hadn't found the original unsolved problem
> posted on this forum then I guess that I would have isolated what caused
> this instead of assuming that there was a bug.
> Thanks for your help Chris,
> cheers.
>
DOS 'setx' in batch file "A" will affect all subsequently invoked batch 
files from outside "A".
Is this what you did? 'setx' can also be invoked from shell scripts but 
still only impacts
subsequently invoked shells. In both cases, the results obtain even 
after reboot.

The GUI way to invoke these "environmental variables is:

Control Panel (Classic View) / System / Advanced Systems Settings / 
Environment Variables / ...

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