From: Daniel Colascione <dancol@dancol.org>
To: James Cloos <cloos@jhcloos.com>
Cc: Emacs discussions <emacs-devel@gnu.org>
Subject: Re: file://host/location URLs
Date: Fri, 16 Nov 2012 19:00:39 -0800 [thread overview]
Message-ID: <50A6FDD7.4090304@dancol.org> (raw)
In-Reply-To: <m3fw49hwnw.fsf@carbon.jhcloos.org>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
On 11/16/2012 4:58 PM, James Cloos wrote:
>>>>>> "DC" == Daniel Colascione <dancol@dancol.org> writes:
>
> DC> In fact, I really don't see why file:// URLs should go through
> DC> url-handlers.el at all. A file URL should be a simple pass-through
> DC> to the normal file handler machinery, yes?
>
> Only file:/// or file://localhost/ should point to the local
> filesystem. file://example.org/foo.bar is a valid uri to some
> resource on example.org using some (unspecified) access method.
It's elegant in theory to make URIs network-transparent, but in practice,
"file:" always refers to a local file. Nobody constructs a file URI intending to
refer to a remote resource not accessible through ordinary filesystem mounts,
and plenty of people accidentally construct file URIs with enough leading
slashes to convince Emacs that a resource is remote. Until I fixed it, our
drag-and-drop code did just that.
If anyone actually uses remote file URIs, please tell me. Otherwise, I intend to
make "file:" and "file://" strictly equivalent and always local.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
next prev parent reply other threads:[~2012-11-17 3:00 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 [this message]
2012-11-17 8:25 ` Achim Gratz
2012-11-17 20:16 ` James Cloos
2012-11-18 8:12 ` Chong Yidong
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=50A6FDD7.4090304@dancol.org \
--to=dancol@dancol.org \
--cc=cloos@jhcloos.com \
--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).