X-Recipient: archive-cygwin@delorie.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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Z+5iFybsIvGZKlTCaMkvv3/uPxCsmC3dmv1R3zqSFt4FRRaczCdpX
	jvJx1dDQhg99xalM5WVJ7BLXOAtsJyJ3RZ5oh1J9JmCyIzQvkG76A+ZC+ALpC+hl
	HTJ1oz/D0KszJbsgzrIJWltrmec0JGEBrGI/CR2YjCnfpQIbwZJ32Q=
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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=2oXyBNUyXbp57e/mh241YY2OSso=; b=foDF9cy6Edb/ZboU174XX3/PKtgJ
	N/IFdpzJMEXxz/QYxrIJ8V7986VA/kZPEvb3APzNLWPZLf9cr1zPVPcn6TdLNeVb
	vzIO0kK3Wq4uVUdG5DM0c38XrCN7abVWviLvnNiZPx1kZruJsDn0axbOgsGs4/yb
	05pXY/JzxzySkIM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX191A/eWUDP3YjeR2IIsjZLW
Date: Mon, 7 Oct 2013 13:00:44 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.7.25: problem with the cd command in ksh
Message-ID: <20131007170044.GA6778@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <524FB2BB.40608@orange.fr> <CAM9pMnMcQcp4prHqs5Bh1sCt0HGC1zaTcmHEXFPrj_+3ZffjmA@mail.gmail.com> <52512348.1050702@orange.fr> <5251240C.6060805@easynet.fr> <CAM9pMnO9NX0-hpSRy7i-2HyYAXnQC3wXsHeJC_ZBx3cD-vyQaw@mail.gmail.com> <20131006223310.GA3135@ednor.casa.cgf.cx> <525242DE.2060604@orange.fr> <1037355178.20131007135428@mtu-net.ru> <5252E508.1030909@orange.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5252E508.1030909@orange.fr>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Mon, Oct 07, 2013 at 06:44:56PM +0200, Francis ANDRE wrote:
>Hi
>
>Andrey
>
>Le 07/10/2013 11:54, Andrey Repin a ?crit :
>> Greetings, Francis ANDRE!
>>
>>> Can I have a official statement from Cygwin about this? ie that bash is
>>> supporting MS-DOX path by accident and ksh won't and that is not a requirement
>>> of Cygwin?
>>> Or
>>> Can Cygwin adds the understanding of absolute DOS path as a requirement and fix
>>> the ksh stuff?
>> That's a weird request, to say the least.
>> Why not fix your script instead? It's all wrong, from the way it handle
>> variable values, to the way it handle paths.
>> And from my understanding of it, YOU prepending the path manually.
>> And you dare complain?
>Hold on Andrey, the script is not mine, it is a tool provided by Sun for making 
>easier the integration of diff from mercurial. I am just a user that want to 
>make it running. I just change all cd by kcd() by that does not work neither

Regardless of who created the script, we are not going to change Cygwin.
As I said, the whole point of Cygwin is to avoid the use of
Window/MS-DOS things like C:\foo.  Specifically patching programs like ksh
to handle MS-DOS paths is not something that makes sense in that context.

cgf

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

