This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [1.7] Backslash incorrectly triggers DOS style path warning
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 20 Apr 2009 17:14:53 -0400
- Subject: Re: [1.7] Backslash incorrectly triggers DOS style path warning
- References: <49EC78A0.6050602@cornell.edu> <49EC7A7D.2050706@cornell.edu>
- Reply-to: cygwin at cygwin dot com
On Mon, Apr 20, 2009 at 09:37:01AM -0400, Ken Brown wrote:
> On 4/20/2009 9:29 AM, Ken Brown wrote:
>> I just installed the bash-completion package. To see how it worked, I
>> typed
>> $ ssh <TAB>
>> This yielded:
>> $ ssh cygwin warning:
>> MS-DOS style path detected: BEGIN {FS=","}
>> /^\s*[^|\#]/ {for (i=1; i<=2; ++i) { \
>> gsub(" .*$", "", $i); \
>> if ($i ~ /
>> Preferred POSIX equivalent is: BEGIN {FS=","}
>> /^/s*[^|/#]/ {for (i=1; i<=2; ++i) { /
>> gsub(" .*$", "", $i); /
>> if ($i ~ /
>> 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
>> Apparently a line continuation backslash in /etc/bash_completion was
>> misinterpreted as an attempt to use DOS style paths.
>
> Sorry, it might not have been the line continuation backslash. There are
> earlier backslashes in the line.
It isn't really erroneous. Something (awk) is trying to open a filename
with that includes backslashes, so cygwin1.dll thinks that it is trying
to open a DOS path.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/