This is the mail archive of the
mailing list for the Cygwin project.
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 21 Jun 2013 17:11:27 -0400
- Subject: Re: dosfilewarning
- References: <51C4AA0B dot 60504 at cygwin dot com> <0D835E9B9CD07F40A48423F80D3B5A7021D8C217 at USA7109MB022 dot na dot xerox dot net>
- Reply-to: cygwin at cygwin dot com
On 6/21/2013 3:47 PM, Nellis, Kenneth wrote:
From: Larry Hall (Cygwin)
On 6/21/2013 2:38 PM, Nellis, Kenneth wrote:
I have a BAT file that calls a bash script that generates the
MS-DOS style path detected: XXX
Preferred POSIX equivalent is: XXX
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
If I rerun the script, I don't get the message a second time, which
makes debugging the problem a problem. How can I have this message
show up on every invocation? I tried closing all Cygwin processes
and tried setting CYGWIN=dosfilewarning, but it seemed to want
It's not designed to do that. It will show up once per Cygwin DLL
session only. If you want to see something different, you'll need
to patch the Cygwin source.
Thanx, but isn't the end of a "Cygwin DLL session" when all processes
that use the Cygwin DLL have terminated?
Yes, that's correct. If you're not getting the message, you still have a
process somewhere keeping the DLL in memory.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple