X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 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: <20090421235020.GA593@ednor.casa.cgf.cx> 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> <20090421235020 DOT GA593 AT ednor DOT casa DOT cgf DOT cx> Date: Tue, 21 Apr 2009 20:00:17 -0400 Message-ID: Subject: Re: [1.7] Backslash incorrectly triggers DOS style path warning From: "Mark J. Reed" To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 7:50 PM, Christopher Faylor wrote: > Cygwin isn't scanning command lines looking for backslashes to scold you > about. Glad to hear it > =C2=A0The 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. --=20 Mark J. Reed -- 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/