Re: w3m doesn't display messages with text/html mime-type properly

[Ted Zlatanov <tzz@xxxxxxxxxxxx>]

On Tue, 22 Apr 2003, yamaoka@jpl.org wrote:
> In the area of the article buffer rendered by emacs-w3m, the TAB
> key is assigned to the `w3m-next-anchor' command, since the
> `w3m-minor-mode' is activated there.  As you've experienced,
> some keys in the `w3m-minor-mode-map' can't be used for the Gnus
> commands.  However, those commands are very useful to stroll
> through the text/html area.  I hope users get acclimated to the
> feature. :)

Can you take a look at the attached message?  It was generated by the
nnrss Gnus backend.  It's invalid HTML, I think.

It triggers a bug in emacs-w3m where TAB in the headers or in the body
locks up Emacs.  I believe Up and Down arrows also lock up Emacs, but
you have to be on the link to trigger that.

Thanks
Ted

Mime-Version: 1.0
Content-Type: text/html
Newsgroups: Linux Today
Subject: developerWorks: Metaclass Programming in Python
Date: Fri, 11 Apr 2003 13:42:16 -0400
Message-ID: <1289@Linux Today.nnrss>

"Most readers are already familiar with the concepts of
object-oriented programming: inheritance, encapsulation,
polymorphism. But the creation of objects of a given class, with
certain parents, is usually thought of as a 'just so' operation. It
turns out that a number of new programming constructs become either
easier, or possible at all, when you can customize the process of
object creation..."

<p><a href='http://linuxtoday.com/news_story.php3?ltsn=2003-04-11-004-26-OS-HL-DV'>link</a></p>