public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: dosfilewarning
Date: Fri, 21 Jun 2013 22:10:00 -0000	[thread overview]
Message-ID: <51C4C17F.7050104@cygwin.com> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A7021D8C217@USA7109MB022.na.xerox.net>

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
>>> following (edited):
>>>
>>> cygwin warning:
>>>     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:
>>>       http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
>>>
>>> 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
>>> something more.
>>
>> 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.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > 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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-06-21 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 18:50 dosfilewarning Nellis, Kenneth
2013-06-21 19:47 ` dosfilewarning Larry Hall (Cygwin)
2013-06-21 20:04   ` dosfilewarning Nellis, Kenneth
2013-06-21 22:10     ` Larry Hall (Cygwin) [this message]
2013-06-22 15:39       ` dosfilewarning 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=51C4C17F.7050104@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --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).