X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20090420211453.GB3143@ednor.casa.cgf.cx> References: <49EC78A0.6050602@cornell.edu> <49EC7A7D.2050706@cornell.edu> <20090420211453.GB3143@ednor.casa.cgf.cx> Date: Tue, 21 Apr 2009 19:41:06 -0400 Message-ID: Subject: Re: [1.7] Backslash incorrectly triggers DOS style path warning From: "Mark J. Reed" To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Monday, April 20, 2009, Christopher Faylor wrote: > It isn't really erroneous. =C2=A0Something (awk) is trying to open a file= name > 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... -- 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/