From: Mathias Dahl <brakjoller@gmail.com>
Subject: Re: What to do about "Bad URL syntax"?
Date: Tue, 13 Sep 2005 17:29:29 +0200 [thread overview]
Message-ID: <umzmh0yw6.fsf__45266.7125886821$1138671361$gmane$org@gmail.com> (raw)
In-Reply-To: <ur7bt13os.fsf@gmail.com>
Mathias Dahl <brakjoller@gmail.com> writes:
> From time to time I get only the text "Bad URL syntax" as message
> body when reading news. After a while I figured out that it probably
> is because the message is a HTML-message. Not sure though, but I can
> read the same post using a "normal" news-reader, and the times I
> have bothered to check it has been HTML-messages.
OK, I will reply to my own post here:
I could not resist trying to debug this problem. It took two hours and
I had to learn about stuff called Edebug and instrumenting functions
for debugging in the process... :)
It seems the root of the problem is when the mime content is to be
rendered or washed. In my case links was called and it could not parse
the HTML given. Hence the "Bad URL syntax" message, which was from
links.
I copied the file that could not be parse on Windows XP, to my
GNU/Linux box at home and there "links -dump" could grok the
content. Strange...
Anyway, I wanted to solve it so I just tried to see if maybe lynx
would work better. After a while of debugging I found the very
interesting option `mm-text-html-renderer', which I could set to lynx
instead of the default links. This solved my problem and I seem to now
be able to also read HTML-postings in GNUS. Yay!
/Mathias
prev parent reply other threads:[~2005-09-13 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 13:45 Mathias Dahl
2005-09-13 15:29 ` Mathias Dahl [this message]
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='umzmh0yw6.fsf__45266.7125886821$1138671361$gmane$org@gmail.com' \
--to=brakjoller@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.
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).