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=OQ
	wyW8ZOV2gbDHQUbMuHnwynulsL8YXxzfzP2zNhejk+1Aov7f2JI9EpgLzutwFFO3
	upauontzqeS50Zto4gqQj2gxNVI+x0z1qTUmr2iEdx3fHwh6tuj/l/QQv6kGbekb
	DGjF8acre0APUIY9TNLTXe47Alfdrx8mbSF6A1nec=
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: <5251240C.6060805@easynet.fr>
References: <524FB2BB.40608@orange.fr>	<CAM9pMnMcQcp4prHqs5Bh1sCt0HGC1zaTcmHEXFPrj_+3ZffjmA@mail.gmail.com>	<52512348.1050702@orange.fr>	<5251240C.6060805@easynet.fr>
Date: Sun, 6 Oct 2013 13:06:52 +0200
Message-ID: <CAM9pMnO9NX0-hpSRy7i-2HyYAXnQC3wXsHeJC_ZBx3cD-vyQaw@mail.gmail.com>
Subject: Re: 1.7.25: problem with the cd command in ksh
From: Robert Klemme <shortcutter@googlemail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1

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.

Fact remains: using the Windows JDK on Cygwin is always nasty since
it's a Windows program and communication between scripts which use
Unix style paths and programs using Windows style paths soon gets
messy - especially if paths need to go both ways.

For your ksh script the easiest fix would probably be

cd $(cygpath -u "$dir")

If it needs to be cross platform you probably need to spend a bit more
effort e.g. define a shell function dependent on the platform where
the Unix versions just return the argument and the Cygwin version does
the mentioned conversion.

Kind regards

robert


-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

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