This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: allow executing a path in backslash notation
On 10 March 2010 10:46, Shaddy Baddah:
>> 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.
http://www.gnu.org/software/bash/manual/bashref.html#Double-Quotes:
The backslash retains its special meaning only when followed by one of
the following characters: â$â, â`â, â"â, â\â, or newline.
Andy
--
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