[1.7] Backslash incorrectly triggers DOS style path warning

[Ken Brown]

On 4/21/2009 10:06 PM, Dave Korn wrote:
> 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?

The text in question is in the definition of _known_hosts() in 
/etc/bash_completion, in case someone wants to try to sort this out.

Ken

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