Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Subject: RE: URL paths in setup.exe Date: Tue, 7 May 2002 22:05:38 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-Has-Attach: content-class: urn:content-classes:message X-MS-TNEF-Correlator: From: "Robert Collins" To: "Earnie Boyd" Cc: "Pavel Tsekov" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g47C7Di28152 > -----Original Message----- > From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com] > Sent: Tuesday, May 07, 2002 9:55 PM > > file:///d/foo/bar.txt on Cygwin should work as well depending on the cygdrive value. ;) file:///d:/foo/bar.txt should be the >win32 mechanism. : has special meaning in url's, which is why MS and netscape use | to represent : for file:// URL's. As for /d|/ , the leading / is irrelevant, the d| makes it absolute regardless. Relative URL's don't actually have a scheme, but they only have meaning in a given context, so we need to stretch the standard a little. > > file://d/foo/bar.txt is definitely relative to the current working directory. Yeah, that's the way I see it, but the URL spec doesn't :[. So we need a compromise, because it's us developers who need to understand whats going on easily. Rob