From: Autotoonz <david.topley@acma.gov.au>
To: cygwin@cygwin.com
Subject: Re: nodosfilewarning not working
Date: Wed, 13 Oct 2010 01:24:00 -0000 [thread overview]
Message-ID: <29948823.post@talk.nabble.com> (raw)
In-Reply-To: <20101013011127.GA14097@ednor.casa.cgf.cx>
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
next prev parent reply other threads:[~2010-10-13 1:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 0:49 Autotoonz
2010-10-13 1:11 ` Christopher Faylor
2010-10-13 1:20 ` Tim Daneliuk
2010-10-13 1:29 ` Autotoonz
2010-10-13 2:35 ` Andrey Repin
2010-10-13 5:30 ` Christopher Faylor
2010-10-13 1:24 ` Autotoonz [this message]
2010-10-13 1:41 ` Christopher Faylor
2010-10-13 1:59 ` Autotoonz
2010-10-13 5:37 ` Christopher Faylor
2010-10-13 5:58 ` Autotoonz
2010-10-13 7:02 ` Lee D. Rothstein
2010-10-13 7:14 ` Autotoonz
2010-10-13 14:50 ` Andrey Repin
2010-10-14 1:45 ` Autotoonz
2010-10-13 1:53 ` Andrew DeFaria
2010-10-13 2:10 ` Autotoonz
2010-10-13 2:29 ` Andrew DeFaria
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29948823.post@talk.nabble.com \
--to=david.topley@acma.gov.au \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).