all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: "Jan Djärv" <jan.h.d@swipnet.se>,
	emacs-devel@gnu.org, "Jason Rumney" <jasonr@gnu.org>
Subject: Re: Patch for remote files in dnd.el
Date: Fri, 08 Sep 2006 09:56:31 +0900	[thread overview]
Message-ID: <wlbqpryy4g.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <33097.128.165.123.18.1157644237.squirrel@webmail.lanl.gov>

>>>>> On Thu, 7 Sep 2006 08:50:37 -0700 (PDT), "Stuart D. Herring" <herring@lanl.gov> said:

>> I'm not sure if file:////REMOTEHOST/DIRECTORY/NAME or
>> file://localhost//REMOTEHOST/DIRECTORY/NAME is invalid or not.  But
>> even the current code uses invalid file:/DIRECTORY/FILE. :-)

> See RFC 3986, section 3.2.2.  file:/dir/file is equivalent to
> file:///dir/file and to file://localhost/dir/file.

Ah, I thought that the latest definition of file: URL was in RFC 1738.
Thanks for the info.

RFC 1738 says:

  A file URL takes the form:

       file://<host>/<path>

  As a special case, <host> can be the string "localhost" or the empty
  string; this is interpreted as `the machine from which the URL is
  being interpreted'.

RFC 3986 says:

  If the URI scheme defines a default for host, then that default
  applies when the host subcomponent is undefined or when the
  registered name is empty (zero length).  For example, the "file" URI
  scheme is defined so that no authority, an empty host, and
  "localhost" all mean the end-user's machine, whereas the "http"
  scheme considers a missing authority or empty host invalid.

The latter mentions the "no authority" case, indeed.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp

  reply	other threads:[~2006-09-08  0:56 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 22:22 Patch for remote files in dnd.el Jason Rumney
2006-07-28  7:25 ` Mathias Dahl
2006-07-28 12:37   ` Jason Rumney
2006-08-01 12:10     ` Mathias Dahl
2006-07-28 10:44 ` Jan Djärv
2006-07-28 11:32   ` Jason Rumney
2006-07-28 13:34 ` Richard Stallman
2006-07-28 19:04   ` Jason Rumney
2006-07-28 22:20     ` Jason Rumney
2006-07-29 17:10       ` Stefan Monnier
2006-08-01  4:58         ` Jan Djärv
2006-08-08  9:38         ` Jan Djärv
2006-07-29  2:59     ` Richard Stallman
2006-09-06 11:15 ` Jan Djärv
2006-09-06 11:31   ` David Kastrup
2006-09-06 11:48     ` Jason Rumney
2006-09-06 11:59       ` David Kastrup
2006-09-06 12:06     ` Jan Djärv
2006-09-06 13:03       ` Reiner Steib
2006-09-06 14:25         ` Michael Albinus
2006-09-07  6:54           ` Richard Stallman
2006-09-07  7:40             ` Michael Albinus
2006-09-06 14:13       ` Michael Albinus
2006-09-07  6:54   ` Richard Stallman
2006-09-07  7:31 ` YAMAMOTO Mitsuharu
2006-09-07  8:12   ` Jason Rumney
2006-09-07  8:25     ` YAMAMOTO Mitsuharu
2006-09-07  8:56       ` Jan Djärv
2006-09-07 15:50       ` Stuart D. Herring
2006-09-08  0:56         ` YAMAMOTO Mitsuharu [this message]
2006-09-07  8:25     ` Jan Djärv
     [not found]       ` <f7ccd24b0609070236r224ce34fobb9ceb0856a3ec39@mail.gmail.com>
     [not found]         ` <44FFED66.2060806@swipnet.se>
2006-09-07 10:01           ` Jan Djärv
2006-09-07 14:13       ` Stefan Monnier
2006-09-07  8:32     ` David Kastrup
2006-09-07  8:49       ` Jason Rumney
2006-09-08 11:55         ` Richard Stallman
2006-09-08 12:43           ` Jason Rumney
2006-09-08 13:01           ` Jan Djärv
2006-09-08 16:45             ` Richard Stallman
2006-09-09  6:25               ` Jan Djärv
2006-09-08 11:55     ` Richard Stallman
2006-09-08 11:55   ` Richard Stallman
2006-09-07 23:47 ` KOBAYASHI Yasuhiro
2006-09-08  8:25   ` Jason Rumney
2006-09-08  9:09     ` YAMAMOTO Mitsuharu
2006-09-15  7:11   ` Jan Djärv
2006-09-15  9:22     ` Jason Rumney
2006-09-15  9:29       ` Jan Djärv
2006-09-15 11:01         ` Jason Rumney

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=wlbqpryy4g.wl%mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=jasonr@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 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.