From: Carsten Dominik <firstname.lastname@example.org>
To: Christopher League <email@example.com>
Subject: Re: [PATCH] fix org-feed when retrieve-method is curl or wget
Date: Tue, 30 Jun 2009 19:40:16 +0200 [thread overview]
Message-ID: <6E8C4D52-2874-4076-9BEE-FB5D8FB43278@gmail.com> (raw)
On Jun 30, 2009, at 5:59 PM, Christopher League wrote:
> Hi Carsten and everyone. I love using org-feed, to gather various
> collection points (delicious, starred in google reader, dial2do,
> etc) into org-mode.
> I tried switching the org-feed-retrieve-method to curl or wget, and
> encountered some bugs. The fixes were simple, and the full details
> are in the attached git patch.
> The problem I was trying to solve, however, was that delicious.com
> would return a "500 server error" sometimes with url.el, and I'm not
> sure why. It returns RSS content anyway, with the error message as
> an <item>. Org-feed doesn't notice the HTTP response status, and
> processes the error as if it were a legit item (which means that
> next time the error occurs, it is silent). Now that I got curl
> working, the 500 doesn't seem to happen anymore.
> My hypotheses so far: maybe it has something to do with the user-
> agent, or with mangling special characters in the URL. The
> delicious URL contains the '&' argument separator, and when the
> error message comes back, it appears with something like '&amp;'
> in it.. as if it were replaced twice. I haven't traced further, to
> determine if fault lies with url.el or with delicious.com.
> Best wishes
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
prev parent reply other threads:[~2009-06-30 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 15:59 [PATCH] fix org-feed when retrieve-method is curl or wget Christopher League
2009-06-30 17:40 ` Carsten Dominik [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).