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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=VJ
	gxO81SqOG/Oh5mnUX/7bafgnBd5Td97pjFnPnUwZJh1NWjbCY3yMzNz7qDg+Q6FX
	II/+yjBD6Ax1DAuFnth/F0WIo2pcE0eCNupwFUGJvZWPxpLYTCYQMjpuGQ5wz+RK
	DhjD6xMpC4DcYs7hsHAtwp8TNCAkTItJuFLcUvImk=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=V5nTfzkI
	mTci0gts2DLWLeow5ss=; b=L/2exu//OOgU458cFXCk63x6hKnTl81OFIMdoKWp
	aCqdbPnnWRw5xYNsABev/ylA4KmA2QmDBzHjjmb8AxIdco6pXCIx+irvJFrkIcgu
	/Y6aTIdsllRHQQM8FFP0IXvUBQMakVjMhoc180xG2Igg21JkA49RD1XlaAriPfZC
	MjY=
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=0.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-vc0-f178.google.com
MIME-Version:	1.0
X-Received:	by 10.220.106.84 with SMTP id w20mr15642006vco.18.1392612916541; Sun, 16 Feb 2014 20:55:16 -0800 (PST)
In-Reply-To:	<20140217035649.GA5507@ednor.casa.cgf.cx>
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>
Date:	Mon, 17 Feb 2014 10:25:16 +0530
Message-ID:	<CAHDNAGJ29D1wk83XcmDzUg4m71+e6Y6K7A37fPcsWCQ-3OaLtQ@mail.gmail.com>
Subject:	Re: batch script execution failing with 255 exit code in cygwin 1.7.28
From:	Prakash Babu <jprakashbabu31 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

 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.


thanks,
Prakash

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