Randall R Schulz <[EMAIL PROTECTED]> writes: > I'm trying to help you, but you seem insistent on just declaring > Cygwin buggy. It is not and it is possible for you to resolve the > problem. I gave you all the information you need to do so. > > One last time, I'll answer your points...
Randall, of course it's up to you whether to answer or not. Nonetheless, thank you for your comments. For everyone else, I don't claim that cygwin is buggy (although it might be the case). I just trying to understand what's going on and how to solve my very problems. Randall's advice to add CYGWIN=noglob _partially_ solves them (yes, really, it makes 2 BS sufficient then 'bash -c "ls c:\\"' is called via syscall CreateProcess()). But: How to write the following command with _backslashes_ to make it work? Suppose we launch it from bash: bash-2.05$ bash -c "ls c:\\\\cygwin\\\\bin\\\\ls.exe" c:\cygwin\bin\ls.exe bash-2.05$ bash -c "c:\\\\cygwin\\\\bin\\\\ls.exe" bash: c:\cygwin\bin\ls.exe: command not found bash-2.05$ CYGWIN=noglob does _not_ help. How many backslahes should I put there? But please check that it _really_ works before answering. Hope to hear from you soon, Dmitry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
