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: <29948823.post@talk.nabble.com> Date: Tue, 12 Oct 2010 18:24:43 -0700 (PDT) From: Autotoonz To: cygwin AT cygwin DOT com Subject: Re: nodosfilewarning not working In-Reply-To: <20101013011127.GA14097@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> 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: > > It's best to eschew the annoyance and conspiracy theories if you don't > completely understand what's going on and actually want help. > A fair comment, although I'm still puzzled as to how nobody can explain why this fails > Something like this works fine: > > c:\>bash > bash$ export CYGWIN=nodosfilewarning > bash$ cat "c:\autoexec.bat" > Unfortunately we are using batch files to automate the running of scripts > and so does: > > 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? -- View this message in context: http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29948823.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