From: Juanma Barranquero <lekktu@gmail.com>
To: Jason Rumney <jasonr@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 6339@debbugs.gnu.org
Subject: bug#6339: url-filename => "/c:/some/file.txt"
Date: Sat, 24 Sep 2011 11:06:58 +0200 [thread overview]
Message-ID: <CAAeL0SR6+g3xvmPeW0nRsnztQS=8R4x9xSvdZR5sJN2foC9LrA@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0STbrQcfQjatgZong+pBCAv8XkGsBiC9Z1kYeY4CyphmJg@mail.gmail.com>
On Sat, Sep 24, 2011 at 10:59, Juanma Barranquero <lekktu@gmail.com> wrote:
> You can argue
> that, in POSIX, "some/file.txt" is an absolute path, because all PATH
> parts of file: URIs must be understood as such (and so, have an
> implicit / at the front),
I mean that "some/file.txt" is an absolute path, in the context of
decoding and splitting an URI, of course. Obviously it is not in
general terms.
That said, I suppose that people who thinks that the third slash is
not a separator, but part of the PATH, should also be arguing in favor
of Windows-style file: URIs being of the form
"file://C:/some/file.txt" (which is clearly incorrect, according to
the spec, and certainly unused in the wild). What does not make sense
is arguing that the value returned by url-generic-parse-url is
correct.
Juanma
next prev parent reply other threads:[~2011-09-24 9:06 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 2:38 bug#6339: url-filename => "/c:/some/file.txt" Lennart Borgman
2010-06-03 11:13 ` Juanma Barranquero
2010-07-26 11:50 ` Juanma Barranquero
2010-07-26 12:00 ` Lennart Borgman
2010-08-01 18:46 ` Juanma Barranquero
2010-08-02 7:51 ` Michael Albinus
2011-09-21 20:28 ` Lars Magne Ingebrigtsen
2011-09-21 22:21 ` Juanma Barranquero
2011-09-21 22:31 ` Lennart Borgman
2011-09-21 22:45 ` Juanma Barranquero
2011-09-21 22:51 ` Lennart Borgman
2011-09-21 22:59 ` Juanma Barranquero
2011-09-21 23:15 ` Lennart Borgman
2011-09-21 23:18 ` Juanma Barranquero
2011-09-21 23:32 ` Lennart Borgman
2011-09-21 23:37 ` Juanma Barranquero
2011-09-21 23:46 ` Lennart Borgman
2011-09-22 0:32 ` Juanma Barranquero
2011-09-22 0:40 ` Lennart Borgman
2011-09-22 0:59 ` Juanma Barranquero
2011-09-22 1:07 ` Lennart Borgman
2011-09-22 1:14 ` Juanma Barranquero
2011-09-22 9:52 ` Lennart Borgman
2011-10-06 5:09 ` Kevin Rodgers
2011-10-06 11:56 ` Juanma Barranquero
2011-10-06 12:43 ` Stefan Monnier
2011-10-06 13:40 ` Juanma Barranquero
2011-10-06 14:24 ` Jason Rumney
2011-10-06 14:30 ` Juanma Barranquero
2011-10-06 14:38 ` Jason Rumney
2011-10-06 14:49 ` Juanma Barranquero
2011-10-06 15:08 ` Lennart Borgman
2011-10-06 15:08 ` Lennart Borgman
2011-10-06 15:31 ` Stefan Monnier
2011-10-06 15:56 ` Juanma Barranquero
2011-10-06 16:49 ` Stefan Monnier
2011-10-06 16:54 ` Juanma Barranquero
2011-10-06 21:08 ` Stefan Monnier
2011-09-24 3:35 ` Jason Rumney
2011-09-24 8:59 ` Juanma Barranquero
2011-09-24 9:06 ` Juanma Barranquero [this message]
2011-09-24 11:53 ` Andreas Schwab
2011-09-24 21:56 ` Juanma Barranquero
2011-09-24 23:42 ` Andreas Schwab
2011-09-25 0:02 ` Juanma Barranquero
2011-09-24 9:46 ` Lennart Borgman
2011-09-24 12:28 ` Richard Stallman
2012-05-09 9:04 ` Chong Yidong
2012-05-09 11:52 ` Juanma Barranquero
2012-05-10 14:15 ` Chong Yidong
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='CAAeL0SR6+g3xvmPeW0nRsnztQS=8R4x9xSvdZR5sJN2foC9LrA@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=6339@debbugs.gnu.org \
--cc=jasonr@gnu.org \
--cc=larsi@gnus.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).