unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] emacs-26 7a8f22b: * test/lisp/url/url-file-tests.el (url-file): Use file:///, not file://.
Date: Thu, 27 Jun 2019 23:37:19 +0000	[thread overview]
Message-ID: <012f2cd6-10c7-4960-72e2-7a773bd5d4f8@cornell.edu> (raw)
In-Reply-To: <CAAeL0SQyUc-M4favEpCprmHjp6rw6dqgdBu6JpXOp03TjJRhuw@mail.gmail.com>

On 6/27/2019 6:30 PM, Juanma Barranquero wrote:
> 
> On Thu, Jun 27, 2019 at 11:57 PM Ken Brown <kbrown@cornell.edu 
> <mailto:kbrown@cornell.edu>> wrote:
> 
>  > This change causes the test to fail on Cygwin.  I think the original "file://"
>  > is the correct prefix.  If concatenated with "/some/file", it yields the URL
>  > "file:///some/file".  Your version with "file:///" as the prefix yields
>  > "file:////some/file", which would refer to a local file "//some/file".
> 
> It's a long-standing issue. The standard says that two slashes are to be 
> followed by a hostname, Three slashes, if there's no hostname.
> 
> So, in fact, Posix apps should strip the initial slash of an absolute pathname 
> before concatenating it to file:///
> 
> https://tools.ietf.org/html/rfc8089
> 
>     Appendix B.  Example URIs
>         The syntax in Section 2 is intended to support file URIs that take
>         the following forms:
>         Local files:
>         o  A traditional file URI for a local file with an empty authority.
>            This is the most common format in use today.  For example:
>            *  "file:///path/to/file"

This is exactly what I said.  From the context, I think it's clear that the 
words "path", "to", and "file" don't contain slashes.

There are four examples in the RFC with four slashes, and in every case it's 
explicitly stated that the URI represents a UNC string.

Ken

  reply	other threads:[~2019-06-27 23:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190615033014.12012.75126@vcs0.savannah.gnu.org>
     [not found] ` <20190615033015.46910210EC@vcs0.savannah.gnu.org>
2019-06-27 21:57   ` [Emacs-diffs] emacs-26 7a8f22b: * test/lisp/url/url-file-tests.el (url-file): Use file:///, not file:// Ken Brown
2019-06-27 22:30     ` Juanma Barranquero
2019-06-27 23:37       ` Ken Brown [this message]
2019-06-28  1:22         ` Juanma Barranquero
2019-06-28  3:13           ` Ken Brown
2019-06-28  4:08             ` Juanma Barranquero
2019-06-28 12:55               ` Ken Brown
2019-06-28 13:00                 ` Juanma Barranquero
2019-06-28 13:17                   ` Ken Brown
2019-06-28 13:23                     ` Juanma Barranquero
2019-06-28 17:27                       ` Ken Brown
2019-06-27 23:48   ` Stefan Monnier
2019-06-28  1:25     ` Juanma Barranquero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=012f2cd6-10c7-4960-72e2-7a773bd5d4f8@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).