X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=Rs3PclT
	F7GqWrV1GDfPE3O8NFe+9B85qiVA90gYSaEGh9YJksbpq2PbD4CQ9bI72TxLhVGC
	XIYSSl/7cjLdTP0BlrzP4zSK83V6QbjpjCBxHI/0nMQu4GPcbv/0bn1Vxk0FaMUT
	a5r/jUKBUaiBJSslKFGl7L+kN1jpIxv2CiMQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=v/Mbx/fx1OFCL
	TaEf4t+GJrC6uc=; b=VOQMXaksZM7A673IQD3jvfZbiGUr8A7ubHSOH2qasaD4A
	RuzSXCrrD6YQ+rM62eLEc+D5itYZqzLKh/pOj5iNR3JecdsL7NY0w6qjafOgInRI
	PVj+E15OmKR0ZZBO2eGTZZtDXsBtmXCJitz11q7p47kvLkaNVVumf3oaIId+eA=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.5 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=D*yandex.ru, browsers, CMD, *sigh*
X-HELO:	mail-io0-f180.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=SB+EJu4eor1KsZFlt+JeSKmXmz30K3fTqMNFDqaXdf0=; b=M6KWS8FJPG/N71Y4IcKkRMXxSqmE2OMiyIuAa0/v04X4h7YcXoxrnqibpRzfo+61hd 0WlwT6fQ0bOrzvT7E5XffWBfsm9NDseaxmca2y/IkJBIvICkiv71bXhkYe2QJQ6/iGuH i8rjsA2lVsXWm/CSzTcODfz1BfwjUfvpM0J4xVKgzinmd0Nmg3gYq6DbJ6y9J42DYVuq hnSkBTh3lgVJc0tTwpjgo8yZMPlD/xV7Esw54enqov9Fos5K/MCa3Wj9+yay58exIVin 5UZQug8T31oeu8JfWFyjVIL+9PCx9DMlY2xFVEYqmcuFnOIcHdEljwFs5YOT+G3NHfPF TA/Q==
X-Gm-Message-State:	ALyK8tJ7l43L2YQM6Fzdx/5gmoxZrO8MOip42964szYL+pCX69Xy/I5cim38s1PPgJ9vyUxiCxM5Tyk0LcTwFg==
X-Received:	by 10.107.175.1 with SMTP id y1mr8312310ioe.137.1467998298935; Fri, 08 Jul 2016 10:18:18 -0700 (PDT)
MIME-Version:	1.0
In-Reply-To:	<217827636.20160707204345@yandex.ru>
References:	<CAPTiy3MdAdrLnLY5C3+Ye48=eyha_+XW=CEdZBJHodvxJjsGrA AT mail DOT gmail DOT com> <c0862cea-a04a-d50c-e632-33748529090f AT gmail DOT com> <CAPTiy3MMUfDQjDt9D=OBMdLy7KNGhdS5a3AdHS4coTamDZ7Tww AT mail DOT gmail DOT com> <loom DOT 20160705T200540-33 AT post DOT gmane DOT org> <85901248 DOT 20160707173235 AT yandex DOT ru> <loom DOT 20160707T180447-900 AT post DOT gmane DOT org> <217827636 DOT 20160707204345 AT yandex DOT ru>
From:	Gene Pavlovsky <gene DOT pavlovsky AT gmail DOT com>
Date:	Fri, 8 Jul 2016 20:18:18 +0300
Message-ID:	<CAPTiy3NT=01MTYXYtMKzR=tQVb080aWiBqqhi756MpB+YAin6w@mail.gmail.com>
Subject:	Re: cygstart.exe can't open file:///C:/
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

Thanks for clarification, guys! Indeed it was my bad for including
customary three forward slashes. Both file://C:/ and file://./C:/ do
work with cygstart.
Appreciate the help.

On 7 July 2016 at 20:43, Andrey Repin <anrdaemon AT yandex DOT ru> wrote:
> Greetings, Brian Inglis!
>
>> Andrey Repin writes:
>>>Brian Inglis writes:
>>>> cygstart file://C:/ works - read the MS DN and MS KB articles on file URIs
>>>> and shlwapi
>>> Which isn't quite right. "file:" is a protocol, "//" is the foreign host
>> mark, "[.]/" is "current host's filesystem root".
>>> So, I guess, the CORRECT solution (or, rather, workaround) would be an
>> explicit "." in host name.
>>> cygstart "file://./C:/"
>>> Works here. Please try it yourself.
>
>> MS approach makes some sense, as the RFCs e.g. 3986 define what you call the
>> the "host" as the namespace authority. In Unix systems, you have only one
>> unified local namespace (even though the mounted filesystems can have
>> radically different namespace rules e.g. fat, ufs, ext?, and the RFCs state
>> the authority may be delegated, so the rules can change along the path),
>> whereas on Windows, each device represents (possibly virtual e.g. subst)
>> separate filesystem namespaces.
>
>> Where MS approach makes no sense, is that . is a (MS) kludge which works,
>> but other local synonyms: null/nothing, localhost, 127.0.0.1, [::1] do not,
>> whereas $BROWSER file://{,.,localhost,127.0.0.1,::1}/C{:,\|} displays
>> identical contents, differing only in whether a : or | follows the drive
>> letter in the address for each tab.
>
> file://localhost/C:/ works, at least for CMD call. Not for cygstart, though.
> Using IP, of course, does not, which, again, makes sense.
> Browsers, on the other hand, often have their own protocol translation, so you
> can't quite compare their behavior to native API calls.
>
>> I dealt with a Windows product where file: (but not ftp, http, or https) had
>> to have an initial cap File: to work. The vendor accepted a bug report but
>> made it a doc issue rather than doing a non-compliance fix. The company
>> and/or products were traded annually  like an end of career player!
>
> *sigh*
>
>
> --
> With best regards,
> Andrey Repin
> Thursday, July 7, 2016 20:38:24
>
> Sorry for my terrible english...
>
>
> --
> 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
>

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

- Raw text -