X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49EE7BC1.1070400@gmail.com> Date: Wed, 22 Apr 2009 03:06:57 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [1.7] Backslash incorrectly triggers DOS style path warning References: <49EC78A0.6050602@cornell.edu> <49EC7A7D.2050706@cornell.edu> <20090420211453.GB3143@ednor.casa.cgf.cx> <20090421235020.GA593@ednor.casa.cgf.cx> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Mark J. Reed wrote: > On Tue, Apr 21, 2009 at 7:50 PM, Christopher Faylor wrote: >> Cygwin isn't scanning command lines looking for backslashes to scold you >> about. > > Glad to hear it > >> 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. > > Got it. So the bug is not in Cygwin, but in some shell function in > the completion setup, which is passing an awk program incorrectly, > causing awk to treat the program text as a filename. > It is maybe getting globbed on the command-line because not protected by quoting and it contains pattern match chars? cheers, DaveK -- 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/