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. -- Mark J. Reed <markjr...@gmail.com> -- 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/
