Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <200104041458.f34Ewm418282@dymwsm11.mailwatch.com>
From: "Fleischer, Karsten (K.)" <kfleisc1@getrag-ford.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: How to (dynamically) control Unix/Dos PATH-like variable
 tran slation
Date: Wed, 4 Apr 2001 10:54:00 -0400
MIME-Version: 1.0
Content-Type: text/plain; 
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit

> Also, most Cygwin programs should be able to deal just fine 
> with Windows
> style paths.  So, just use those.

ksh93 has a variable type for automatically converting UNIX pathnames to
Windows pathnames.
This is an excerpt from the documentation for the typeset command of ksh:

--8<--
       -H     Hostname  mapping.  Each  name holds a native path-
              name. Assigning a UNIX format pathname  will  cause
              it  to  be converted to a pathname suitable for the
              current host. This has no effect  when  the  native
              system is UNIX.

--8<--

So I'd rather suggest patching bash to support this kind of variables than
anything else. Or to port ksh (which would also mean to port the AT&T AST
library first).
Or, just use Windows paths, as Chris suggested.

Karsten


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple