Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Server-Uuid:	c41a640a-a9e9-11d4-8124-00508bd3f8dc
Message-ID:	<200104041458.f34Ewm418282@dymwsm11.mailwatch.com>
From:	"Fleischer, Karsten (K.)" <kfleisc1 AT getrag-ford DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT 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
X-Mailer:	Internet Mail Service (5.5.2651.58)
X-WSS-ID:	16D5E924715935-01-01

> 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

- Raw text -