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: <29948847.post@talk.nabble.com> Date: Tue, 12 Oct 2010 18:28:59 -0700 (PDT) From: Autotoonz To: cygwin AT cygwin DOT com Subject: Re: nodosfilewarning not working In-Reply-To: <4CB5093E.4010103@tundraware.com> 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> <4CB5093E DOT 4010103 AT tundraware DOT com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Tim Daneliuk wrote: > > You can also permanently set this environment variable from Windows itself > so > that all instantiations of cygwin environments - regardless of shell will > see it. > No I can't, as stated in the OP. Also, this is no use for surpressing the warning when running individual scripts -- View this message in context: http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29948847.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