From: Juanma Barranquero <lekktu@gmail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 6339@debbugs.gnu.org
Subject: bug#6339: url-filename => "/c:/some/file.txt"
Date: Thu, 22 Sep 2011 00:45:17 +0200 [thread overview]
Message-ID: <CAAeL0SSK9uF9Vzb7RTct_DGP2D0LsDuHnyWhqQRcY_ca+svTMw@mail.gmail.com> (raw)
In-Reply-To: <CANbX3677gTAOOXRuxfaKHLndP0Hv0qECcArG1_ntUo3tAbzuOQ@mail.gmail.com>
On Thu, Sep 22, 2011 at 00:31, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> Are we not dealing with two different file name syntaxes here that
> just happens to look very similar? I.e. the URL file name syntax and
> the unix style file name syntax.
I would expect that an accessor for the filename slot of a struct
called URL would interpret the struct as a URL, and the "filename" of
the URL does not start with a slash. Why would I expect that
url-filename (url-generic-parse-url, in fact) returns anything "unix
style" specific?
> url-filename is now returning the file name in unix style.
No.
(url-generic-parse-url "file:///C:/my/file.xt") => [cl-struct-url
"file" nil nil "" 21 "/C:/my/file.txt" nil nil t nil]
That's not a "file name in unix style", that's a bug, clear and
simple. There's no reason why url-generic-parse-url should think that
a URL is in some kind of "unix style". What if it is a VMS filename?
> This is, as
> you said, practical, but a bit surprising. I suspect there are some
> small mixing of those syntaxes elsewhere too. My suggestion would be
> to keep them and document them.
"Keep them and document them" still means that it does not work for
Windows or VMS or anything not POSIX-style. And fixing it just for
these systems means that we keep a bug for POSIX sake and make other
systems jump around hoops. Ugly, to say the least.
Juanma
next prev parent reply other threads:[~2011-09-21 22:45 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 [this message]
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
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=CAAeL0SSK9uF9Vzb7RTct_DGP2D0LsDuHnyWhqQRcY_ca+svTMw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=6339@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=lennart.borgman@gmail.com \
/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).