X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <29949816.post@talk.nabble.com>
Date: Tue, 12 Oct 2010 22:58:03 -0700 (PDT)
From: Autotoonz <david DOT topley AT acma DOT gov DOT au>
To: cygwin AT cygwin DOT com
Subject: Re: nodosfilewarning not working
In-Reply-To: <20101013053646.GA15747@ednor.casa.cgf.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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> <20101013053646 DOT GA15747 AT ednor DOT casa DOT cgf DOT cx>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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



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. 

-- 
View this message in context: http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29949816.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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