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
Message-Id:	<4.3.1.2.20010404114037.0210d2a0@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Wed, 04 Apr 2001 11:47:09 -0400
To:	Glen Coakley <gcoakley AT mqsoftware DOT com>, Cygwin <cygwin AT cygwin DOT com>
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	RE: How to (dynamically) control Unix/Dos PATH-like variable
	tran slation
In-Reply-To:	<E1B42CFD544FD31193EE0000E87C5CE799B4B9@mailserver2.mqsoftw
	are.com>
Mime-Version:	1.0

At 10:26 AM 4/4/2001, Glen Coakley wrote:

>Sorry, it's not dead yet but hopefully this will kill it. 
>
>Chris, I am not sure which programs you are referring to here. Do the
>standard file/path handling functions (open, fopen, etc.) that are in
>cygwin1.dll cope with either type of path? I think you may have some
>information here that the list at-large doesn't.


Really?  I find exactly what Chris has stated here:

http://www.cygwin.com/cygwin-ug-net/using.html#USING-PATHNAMES


See the first line.


>Other users will have to try their OS to find out where else this works.
>but, I just tried using POSIX paths on my Win2000 box and they work just
>fine in cygwin or the Command Prompt. My cygwin root is d:\cygwin. I can
>reference this from a Win2000 command prompt window or a Cygwin bash shell
>as either //d/cygwin or /d/cygwin. 


Not in general, although you can set up your system so this could work.
In any case, Windows apps don't understand the Cygwin mount table so if
the path you specify relies on that, it's not going to work at the Command
Prompt.  Also, although the underlying Win32 APIs understand / and \ as
path separators, Command Prompt only recognizes \.


>So, for those that have the latest MS annoyance (OS) always using the POSIX
>path should work everywhere.


Well, perhaps for you.

Consistent with the opening statement of your email message, let's kill this 
discussion.  Anyone curious about how Cygwin handles paths w.r.t. Windows 
inter-operability can find the information that's been discussed so far (and 
more) in the User's Guide and some in the FAQ as well.




Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


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

- Raw text -