X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Tue, 21 Apr 2009 19:50:20 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [1.7] Backslash incorrectly triggers DOS style path warning
Message-ID:	<20090421235020.GA593@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<49EC78A0 DOT 6050602 AT cornell DOT edu> <49EC7A7D DOT 2050706 AT cornell DOT edu> <20090420211453 DOT GB3143 AT ednor DOT casa DOT cgf DOT cx> <f60fe000904211641l558faa99r957730125f8cd7ab AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<f60fe000904211641l558faa99r957730125f8cd7ab@mail.gmail.com>
User-Agent:	Mutt/1.5.16 (2007-06-09)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 Tue, Apr 21, 2009 at 07:41:06PM -0400, Mark J. Reed wrote:
>On Monday, April 20, 2009, Christopher Faylor wrote:
>> 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.
>
>Except it looks like, from what's pasted above, that it's actually a
>non-filename backslash that's triggering it - the backslash inside an
>awk pattern, in this case.  It's seeing the regex /^\s/ and
>recommending that it be replaced with /^/s/.  Clearly the trigger is
>overzealous...

Clearly you aren't getting this.

Cygwin isn't scanning command lines looking for backslashes to scold you
about.  The line in question was somehow used as an argument to open()
or stat() or access() or some other function which takes a filename
argument.  The fact that a human being can look at the line and conclude
that it isn't a filename is irrelevant.  Cygwin saw a backslash in a
filespec and complained about it.  That's how it works.

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/

- Raw text -