X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_NEUTRAL
X-Spam-Check-By: sourceware.org
Message-ID: <49EC7A7D.2050706@cornell.edu>
Date: Mon, 20 Apr 2009 09:37:01 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [1.7] Backslash incorrectly triggers DOS style path warning
References: <49EC78A0 DOT 6050602 AT cornell DOT edu>
In-Reply-To: <49EC78A0.6050602@cornell.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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.

--
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/