X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.7 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_PD
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <748260321.20111201203028@mtu-net.ru>
References: <4ED74766 DOT 7010301 AT yahoo DOT com>	<748260321 DOT 20111201203028 AT mtu-net DOT ru>
Date: Thu, 1 Dec 2011 14:17:28 -0500
Message-ID: <CAGHJv4ceBgyO7RsBGYO_HOfSUr4fRaZrFytOvMeFOgr+=pXY5w@mail.gmail.com>
Subject: Re: Will win32 style paths ever work in mksh on cygwin?
From: Chris Sutcliffe <ir0nh34d AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Hi All,

I am the mksh maintainer for Cygwin...

On 1 December 2011 11:30, Andrey Repin wrote:
>> Are there any plans to make mksh on cygwin win32-path aware, or will
>> mksh on cygwin support only POSIX?
>
> You have to ask mksh author(s).

I work closely with Thorsten Glaser, who is the mksh author.  His
position is that mksh behaviour should remain consistent across
platforms, as such his expectation is that any scripts run via mksh be
POSIX path compliant (this has come up in the past).

>> If it remains to be POSIX only, and pdksh apparently gone from the list
>> of shells, is the only alternative to rewrite all existing ksh scripts
>> that might use win32 style paths?
>
> The last trend in *NIX society, that I noticed, is to write portable scripts.
> Which means, they should work with /bin/sh. (The base POSIX shell implementation.)

Fundamentally, Cygwin has been pushing the use of POSIX paths for
quite some time (in fact it warns you when it encounters a DOS /
Windows path).  As has been pointed out, many Cygwin utilities support
DOS / Windows paths (likely for historical reasons I suspect), but
mksh will not.

Not the answer you were hoping for I'm sure, but it is where we are at
right now.

Cheers,

Chris

-- 
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d

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