Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: URL + efs confusion
Date: Mon, 15 Nov 2010 21:06:37 +0100	[thread overview]
Message-ID: <m3ipzygxma.fsf@quimbies.gnus.org> (raw)

Sometimes people put local URLs into their RSS feeds, like

<img src="file:/c:/thing/foo">

This ends up as a url call like this:

(url-retrieve "file:/c:/thing/foo" #'ignore)

which ends up prompting me for my ftp password, since c:/thing/foo is
interpreted as an efs file name.

This seems not very optimal.  Could there be situations where that URL
makes sense to interpret that way?  And what about on Windows machines?

Anybody have any suggestions about on what level this should be fixed?
Gnus, shr or url?  And how?  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




             reply	other threads:[~2010-11-15 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 20:06 Lars Magne Ingebrigtsen [this message]
2010-11-15 20:23 ` Ted Zlatanov
2010-11-15 22:45   ` Lars Magne Ingebrigtsen

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=m3ipzygxma.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).