[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: w3m doesn't display messages with text/html mime-type properly
Ted Zlatanov <firstname.lastname@example.org> writes:
> Can you take a look at the attached message? It was generated by the
> nnrss Gnus backend. It's invalid HTML, I think.
Valid or invalid is pretty irrelevant. Invalid HTML shouldn't cause
emacs to get into a loop that only C-g can get out of.
Anyway, as I said before, the issue is not the validity of the HTML
but the fact that this message is "Content-Type: text/html". If you
send a message to yourself from Mozilla Mail without a text/plain
alternative part (i.e. the header of the message has "Content-Type:
text/html"), then you will run into the same problem (but the email
will be completely valid -- including a DOCTYPE).
The stop-gap for nnrss is to create "Content-Type:
multipart/alternative" messages instead of the text/html-only
The long-term solution is to make w3m use widgets (like the rest of
the buffer) instead of having a special keymap just for the body of
I doubt either one of those solutions will be put in place before
release of Oort (because I don't have time to do either). But I may
You are a mystery as deep as the sea; the more I search, the more
I find, and the more I find the more I search for you.
-- St. Catherine of Siena