X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_00,RCVD_NUMERIC_HELO,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew DeFaria Subject: Re: nodosfilewarning not working Date: Tue, 12 Oct 2010 21:53:21 -0400 Lines: 39 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12pre) Gecko/20101011 Lightning/1.0b2 Shredder/3.1.6pre In-Reply-To: <29948823.post@talk.nabble.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 On 10/12/2010 09:24 PM, Autotoonz wrote: > 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 In order to do that we'd need to know exactly what you are doing. Otherwise we're just guessing. You stated "Here is the command line I'm running: C:\cygwin\bin\bash --login C:\test\test.sh" but you didn't allude to how exactly you are running this. If from Start: Run for example, have you tried just running bash --login and then echo'ing out the $CYGWIN environment variable? Have you tried reading up on what is a local environment variable is, how it is set and how it is in effect under Windows? Because it seems to me it's clear that bash doesn't see $CYGWIN as having nodosfilewarning set into it. If it did it would work. Also note that's a long value - are you sure you have typed it correctly (Sorry I don't have access to Windows right now to check this). >> 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 Yes, right. Well stop that! :-) >> 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? 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? -- 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