MIME-Version: 1.0
In-Reply-To: <4B97789F.1060405@shaddybaddah.name>
References: <720660.16774.qm@web88302.mail.re4.yahoo.com> 	 <20100310092536.GS6505@calimero.vinschen.de> 	 <e6940be71003100203h297db699ua44ae9086bf64a72@mail.gmail.com> 	 <4B97789F.1060405@shaddybaddah.name>
Date: Wed, 10 Mar 2010 10:54:08 +0000
Message-ID: <416096c61003100254r754b96efy3fc8b4ea5c7f2908@mail.gmail.com>
Subject: Re: allow executing a path in backslash notation
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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"&& =C2=A0echo 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 =3D s, \c =3D 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: =E2=80=98$=E2=80=99, =E2=80=98`=E2=80=99, =E2=80=
=98"=E2=80=99, =E2=80=98\=E2=80=99, 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