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:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=W8oRMT8oi/LvkOrFZjAalU2J/ygAM0zFZ9QtYGIlBtW
	NC1Qlf1mdb/pSpIhouVGljfY2YTGE06dOlOZ95FbsWcPr+zAE8pwxPD8zXDEqIMP
	/CQ5NozX1RBcVBXo0mpgL/s4u8Y0T1rf7TzNPT1pPXvHwJEawVKMvIbutCL8PyxY
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <525242DE.2060604@orange.fr>
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>
From: Adam Dinwoodie <adam@dinwoodie.org>
Date: Mon, 7 Oct 2013 16:20:49 +0100
Message-ID: <CA+kUOakdECG2XoqOhNmxm49QBYK1EVsRn=PC-Q6KWHFJH4cnnA@mail.gmail.com>
Subject: Re: 1.7.25: problem with the cd command in ksh
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

On 7 October 2013 06:13, Francis ANDRE wrote:
> Le 07/10/2013 00:33, Christopher Faylor a écrit :
>> More likely it is just because ksh automatically prepends the current
>> working directory to something that it considers to be relative.
>>
>> I know I'm a broken record on the subject but it is not a requirement that
>> Cygwin tools to be able to understand MS-DOS paths.  It's possible that
>> they
>> do, by coincidence, understand them but it is not a given that they will.
>
> 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?

cgf is one of the Cygwin project leads. That statement above is about
as official as you can get.

http://cygwin.com/who.html

This is an open-source project. If you want ksh to be able to
understand DOS paths, you're welcome to take the source code and
change it so it does, or to pay someone to do it for you. You could
even submit the patches; if folk like the change (either the Cygwin's
ksh maintainer or ksh's upstream developers) it may make the official
releases and be supported from that point on.

For now, however, simply asking for something to change isn't going to
change it. Having every Cygwin package support DOS paths would be a
fairly major undertaking, and one I doubt anyone would be willing to
take on. Making ksh support them is more feasible, but someone has to
do the work, and I doubt you'll get any volunteers any time soon.

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