X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <29948971.post@talk.nabble.com> Date: Tue, 12 Oct 2010 18:59:26 -0700 (PDT) From: Autotoonz To: cygwin AT cygwin DOT com Subject: Re: nodosfilewarning not working In-Reply-To: <20101013014122.GA14285@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> 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 Christopher Faylor-8 wrote: > > You haven't provided the exact steps to show what doesn't work. This: > >>>On Tue, Oct 12, 2010 at 05:49:31PM -0700, Autotoonz wrote: >>>>Here is the command line I'm running: C:\cygwin\bin\bash --login >>>>C:\test\test.sh > > isn't much to go on. If you just type if from the CMD prompt you get > the expected warning. What, precisely, did you do which you expected > to work? You need to show the exact steps to reproduce the problem. > >>>c:\>set CYGWIN=nodosfilewarning >>>c:\>C:\cygwin\bin\bash --login C:\test\test.sh >>> >>>You may need to create a .bat file if you want to just do the latter. >> >>As per my original post, this most definitely does *not* work. Have >>you tried this yourself yet? > > Yes, I tried it. I tried it from the CMD prompt (which is where I > tested this when I first implemented it) and I tried it from a .bat > file. Both work as expected, i.e., no warning. > > 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! Thanks for your patience, Cheers! -- View this message in context: http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29948971.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