X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<5195c8760901020642g7af8c830w237ee298e645b91f@mail.gmail.com>
Date:	Fri, 2 Jan 2009 20:12:51 +0530
From:	"Jeenu V" <jeenuv AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cmd.exe from Cygwin
In-Reply-To:	<dd5f2deb0901020623o26f5dc9crf9eec2b084f2f4db@mail.gmail.com>
MIME-Version:	1.0
References:	<5195c8760901020359y51dbe19cw2803e36afe028c1d AT mail DOT gmail DOT com> <dd5f2deb0901020623o26f5dc9crf9eec2b084f2f4db AT mail DOT gmail DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Thanks for the reply.

>
> The backslash is an escape character, so you need to get it treated as
> a character somehow - escaping ("\\") or inside quotes works for me:
>

I'm aware of this.

>> N:\src\CEDAR\GENERIC\base\bsp\hwip_arm\rvemuboard\ct1136\test>cmd /c
>> bldmake bldfiles ARMV6
>> sh: E:SymbianM04765_Symbian_OS_v9.5binTechViewepoc32toolsbldmake.bat:
>> command not found

 If you see above example, all I run is a command 'bldmake' which
neither contain back-slash nor white-space. So there's no need to
quote the file name here. What 'bldmake' really is--whether .bat, .com
or .exe--it's for cmd.exe to find out, of course using %PATH%. In my
case, going by the output, it did locate a .bat file with the name
'bldmake'. However, I suspect, something went wrong in the path
translation. But the 'sh: ' in the error output rings in my head.

Talking about black-slashes: assuming it's a .bat file, as long as the
content is interpreted by cmd.exe, the back-slashes inside the script
shouldn't make a difference.

>> It would suffice--as of now, at least--if I could launch a
>> cmd.exe--separate and independent--window from a Cygwin shell. I could
>> try

Update: I tried with cygstart.exe, I don't see a difference from
starting it with cygstart.exe and the above example. I.e. back-slashes
are truncated and output said 'sh: '.

-- 
Thanks
Jeenu

--
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/

- Raw text -