From: Ken Brown <kbrown@cornell.edu>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Juanma Barranquero <lekktu@gmail.com>
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 21:57:04 +0000 [thread overview]
Message-ID: <9c367baa-841d-24e0-1436-1a8f3a3ed081@cornell.edu> (raw)
In-Reply-To: <20190615033015.46910210EC@vcs0.savannah.gnu.org>
On 6/14/2019 11:30 PM, Juanma Barranquero wrote:
> branch: emacs-26
> commit 7a8f22b00484e2c1a28b48767b8562c6b6e89e06
> Author: Juanma Barranquero <lekktu@gmail.com>
> Commit: Juanma Barranquero <lekktu@gmail.com>
>
> * test/lisp/url/url-file-tests.el (url-file): Use file:///, not file://.
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".
Posix says that the meaning of a path name starting with exactly two slashes is
implementation-defined. On Cygwin, it's interpreted as a UNC path name,
referring to a file on a network.
Ken
next parent reply other threads:[~2019-06-27 21:57 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 ` Ken Brown [this message]
2019-06-27 22:30 ` [Emacs-diffs] emacs-26 7a8f22b: * test/lisp/url/url-file-tests.el (url-file): Use file:///, not file:// Juanma Barranquero
2019-06-27 23:37 ` Ken Brown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c367baa-841d-24e0-1436-1a8f3a3ed081@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.