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=hHtll/5D27S1Cf3W+E5n1d63NcnhTjaHiyfoF4EcqCNNQMfuWi6Vi
	oYbdajj9ZGQ2Q5TXX//u5nj6+XriKpACefWjedt5m2cVfXqbwORjKEgzrRgRnyxH
	xMMOINdjyeauKrDNbnadCeqeG0qW56t5Gg29uAc3FV+mtSjMHM3wI0=
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=hxa5QmFtwiWcbTkY8rj7ZuFDcHg=; b=UlbkvzN8zAEYtp/Dd1KdWLMxSJGS
	2U5r5PlkU4kgr9tjijK/EZaO61eYhs8+A+8r0cGpPe0COQInkFQXoz3DnlI1DUUv
	+S0th4A3nmHy1oPR8TsWU8u5LCCtT25DJMxjJ3QxjhqWB6ARJCL6sWvbrfngmZ3F
	ltJ4kN3N5dTlBEo=
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=2.8 required=5.0 tests=AWL,BAYES_20,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: U2FsdGVkX1+BhN3GMMDm3szSRVQ1p1Fd
Date: Sun, 6 Oct 2013 18:33:10 -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: <20131006223310.GA3135@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAM9pMnO9NX0-hpSRy7i-2HyYAXnQC3wXsHeJC_ZBx3cD-vyQaw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Sun, Oct 06, 2013 at 01:06:52PM +0200, Robert Klemme wrote:
>On Sun, Oct 6, 2013 at 10:49 AM, Francis ANDRE <francis.andre@easynet.fr> wrote:
>> Hi Robert
>>
>> The problem here is that the string of the target directory is computed by
>> another tool -- Mercurial in this case -- and that Mercurial returns a
>> absolute windows style path as
>>
>> Z:/DEV/OpenJDK_7u40/hotspot
>>
>> which seems to be relative in Unix world but which is absolute in the
>> Windows world.
>>
>>
>> Moreover, when using the bash shell, the command
>>
>> FrancisANDRE@idefix /cygdrive/c/Cygwin
>> $ cd Z:/DEV/OpenJDK_7u40/hotspot
>>
>> moves the cwd without error to
>> FrancisANDRE@idefix /cygdrive/z/DEV/OpenJDK_7u40/hotspot
>>
>>
>> So why the ksh cannot do the same?
>
>That question ksh developers or cygwin package maintainers should be
>able to answer.  They might just use different syscalls which vary in
>behavior on Cygwin.  You could try to find that out with strace.

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.

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

