From: Chong Yidong <cyd@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: James Cloos <cloos@jhcloos.com>, emacs-devel@gnu.org
Subject: Re: file://host/location URLs
Date: Sun, 18 Nov 2012 16:12:24 +0800 [thread overview]
Message-ID: <877gpje3dj.fsf@gnu.org> (raw)
In-Reply-To: <m3wqxkgf2f.fsf@carbon.jhcloos.org> (James Cloos's message of "Sat, 17 Nov 2012 15:16:31 -0500")
James Cloos <cloos@jhcloos.com> writes:
>>>>>> "AG" == Achim Gratz <Stromeko@nexgo.de> writes:
>
> AG> Common bugs in applications and misconceptions of some users
> AG> notwithstanding, an URI should implement:
>
> AG> http://tools.ietf.org/html/rfc3986
>
> And rfc 1738 for file://’s definition and syntax.
To expand on these points: "file:" and "file://" not equivalent under
RFC 3986, so don't do that.
It seems acceptable to signal an error if a file:// URI specifies a
remote host, instead of using FTP. But if the hostname is that of the
local computer, it ought to work fine. For that reason, I think
url-handlers.el is still needed, and that's where the fix needs to be.
Currently, the url library treats file:// and ftp:// urls as synonymous,
but that can be changed.
next prev parent reply other threads:[~2012-11-18 8:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 23:43 file://host/location URLs Daniel Colascione
2012-11-16 14:18 ` Stefan Monnier
2012-11-17 0:58 ` James Cloos
2012-11-17 3:00 ` Daniel Colascione
2012-11-17 8:25 ` Achim Gratz
2012-11-17 20:16 ` James Cloos
2012-11-18 8:12 ` Chong Yidong [this message]
2012-11-18 15:31 ` Daniel Colascione
2012-11-19 3:54 ` Stephen J. Turnbull
2012-11-19 17:16 ` Achim Gratz
2012-11-20 12:54 ` Jason Rumney
2012-11-20 20:07 ` Daniel Colascione
2012-11-20 20:52 ` Achim Gratz
2012-11-21 6:33 ` joakim
2012-11-21 8:29 ` Andreas Schwab
2012-11-22 8:50 ` joakim
2012-11-18 15:27 ` Stephen J. Turnbull
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=877gpje3dj.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=cloos@jhcloos.com \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
/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).