This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: allow executing a path in backslash notation


Hi,

On 10/03/2010 10:03 AM, Ilya Beylin wrote:
The problem is that DOS paths are treated differently, even within the
same program.
Take for instance, bash:

$ builtin test -x "$WINDIR\system32\cmd.exe"&&  echo ok
yes
$ builtin exec "$WINDIR\system32\cmd.exe" /C echo ok
-bash: exec: C:\WINDOWS\system32\cmd.exe: not found

That makes a lot of headache both for users and for programmers who
have to remember about all such special cases

Is it me, or is the quoting all wrong? Doesn't backslash in the double quote (") acts as an escape character. i.e \s = s, \c = c etc.

So, how is the exec (and apparently test) getting the correct string?

Regards,
Shaddy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]