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