X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=QwAwVLBqWTqV9vb0
	Tz8xaJS8/JNvtCoaXaI9HSaNR3xU9yhPA1UJLjcQzuQaKpiR5VRkbI0ZlQycngZC
	jT6ffACXJcIMA0XCuE3GdOlnISicPWBLyFCyP/ukYyl5AkXJFIrfNpG1y18k7Kp4
	9tDFOVNSmQsgmqKkZa2jm2slTNQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=LhWRc4E5OrzsYiM+eqkTl1
	VVJlY=; b=C6bwPh5uBtZR7CiUwSKYIs8rVK5UvSTQZPE/iSmYigFxu/y8BuRGJg
	z+Gl3lHl+AiJmHnTAkT+refo8HcqdEuZsT6R0QazvZYxoPJrhiPa0Xvyp5m9HIL9
	G3CA6nZWl9/lx4aDCX9a6jk3wYqxxVEO0Dj3hF3gp0fXolyeagIQQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-3.0 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_BL_SPAMCOP_NET,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtpback.ht-systems.ru
Date:	Mon, 17 Feb 2014 09:47:55 +0400
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<492711937.20140217094755@yandex.ru>
To:	Prakash Babu <jprakashbabu31 AT gmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: batch script execution failing with 255 exit code in cygwin 1.7.28
In-Reply-To:	<CAHDNAGJ29D1wk83XcmDzUg4m71+e6Y6K7A37fPcsWCQ-3OaLtQ@mail.gmail.com>
References:	<CAHDNAGKo6SyTV_1sHsLoq6xR0p8BdT-TQ_9P=WCi+8j2dY7oEA AT mail DOT gmail DOT com> <20140214152344 DOT GA1191 AT ednor DOT casa DOT cgf DOT cx> <CAHDNAG+P1JS5DYpKYTeV1XPe8Phh8EKr0+KnqkRM_d7xmgLEiw AT mail DOT gmail DOT com> <20140217033532 DOT GA2376 AT ednor DOT casa DOT cgf DOT cx> <20140217035649 DOT GA5507 AT ednor DOT casa DOT cgf DOT cx> <CAHDNAGJ29D1wk83XcmDzUg4m71+e6Y6K7A37fPcsWCQ-3OaLtQ AT mail DOT gmail DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Prakash Babu!

>  thanks Christopher.
> I found the following archive which introduced this fix
> (http://cygwin.com/ml/cygwin-patches/2014-q1/msg00017.html)

> I feel this causes an inconsistent behavior when batch scripts are
> executed using command interpreter(cmd.exe) and cygwin.
> There are some generic batch script we might give to users where some
> might execute using cmd.exe and some using cygwin(especially remotely
> using ssh) and I would be expecting the same behavior in both places.

> Also my existing batch script handles argument a=b in a way where I
> obtain 'a' using %1 and 'b' using %2 and this behavior is broken now.

I would suggest using bash instead of cmd.
Since you are running SSH anyway, you are likely to have bash, too.
As powerful CMD is, it's cumbersome to use, and nowhere near as powerful, as
POSIX shell, not to mention full power of BASH.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 17.02.2014, <09:44>

Sorry for my terrible english...


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

- Raw text -