Message-ID: <29949009.post@talk.nabble.com>
Date: Tue, 12 Oct 2010 19:10:05 -0700 (PDT)
From: Autotoonz <david.topley@acma.gov.au>
To: cygwin@cygwin.com
Subject: Re: nodosfilewarning not working
In-Reply-To: <i933eh$ibg$1@dough.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <29948673.post@talk.nabble.com> <20101013011127.GA14097@ednor.casa.cgf.cx> <29948823.post@talk.nabble.com> <i933eh$ibg$1@dough.gmane.org>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


defaria wrote:
> 
> Being as Chris is the project manager for Cygwin (and an all around nice 
> and competent guy) I can pretty much guarantee you that yes he did test 
> it. Wait... He just posted and yes he did do it. This leads me to ask - 
> did you try it? Exactly that, what Chris posted? And if you did and it 
> failed can you provide evidence?
> 

Yeah I did try it originally from batch files, but unfortunately I didn't
allow for my batch file calling another batch file and losing the
environment variable.
And because I'd read a previous post about this problem (with no solution),
I wrongly assumed that there was a bug in CYGWIN which nobody cares about.
Otherwise, I would not have jumped the gun here and suggested that it was
punishment to DOS users.
Besides, Windoze and DOS has plenty of punishment for users as it is! :D

-- 
View this message in context: http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29949009.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