From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacs-26 7a8f22b: * test/lisp/url/url-file-tests.el (url-file): Use file:///, not file://.
Date: Fri, 28 Jun 2019 03:25:22 +0200 [thread overview]
Message-ID: <CAAeL0SRiGiVwuLQD4k9BHfjN7Y92Ns3cB4qiiLOXttsdR824Jg@mail.gmail.com> (raw)
In-Reply-To: <jwv7e96r3r0.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Fri, Jun 28, 2019 at 1:49 AM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> So based on this discussion, I guess what this means is that using
> a plain `concat` can't be right: for Windows-style name "c:/foo/bar"
> we should use `(concat "file:///" file)`, whereas for POSIX-style file
> names "/foo/bar" we should use `(concat "file://" file)`.
Strictly speaking, I think POSIX /foo/bar pathnames should be stripped of
the initial slash and then concatenated...
...but yeah, you're right. We need to do different things.
[-- Attachment #2: Type: text/html, Size: 738 bytes --]
prev parent reply other threads:[~2019-06-28 1:25 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
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 [this message]
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=CAAeL0SRiGiVwuLQD4k9BHfjN7Y92Ns3cB4qiiLOXttsdR824Jg@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.