Re: Bugs in PGnus

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Brian May <bmay@csse.monash.edu.au> writes:

> 2. As I already mentioned, threading often has problems, as messages
> are put with the wrong thread. This seems to be because "Y c"
> inserts cached articles at the *current* cursor position, and not in
> thread order. Pushing "T t" on the broken thread fixes it.

Does this only happen with the cached articles, or with the other
similar commands (`j', `^', `M-^') as well?

> 4. I sent myself a HTML file (please ask if you want a copy) that
> displays OK in X-Windows, but in a text-mode console, the top
> of the file is missing,

Could it be that w3 renders the message in a font that's not, er,
visible?

> According to weblint, the "content=" should be quoted. However,
> I didn't write this HTML, so it is outside my control. PGnus
> gets *very* confused and displays:
> 
> html;charset=iso-8859-1 http-equiv=Content-Type>

This has been fixed in more recent versions of w3.

> Another problem with this message is that in text mode xemacs,
> the actual content is invisible (black on black) - probably because the HTML
> sets the background color, but not the foreground color - Stupid!
> No wonder - it is "MSHTML" ;-).

There are w3 variables for customizing a bunch of font things.  Newer
version of w3 are very good at coping with all sorts of totally broken
HTML.

> However, while PGnus will display an entry for the cached article, it
> refuses to display the contents of this article:
> 
> Symbol's value as variable is void: gnus-article-decode-hook

That's very odd.  (Time passes.)  Aha!  It's the old
binding-a-variable-before-its-defvar-is-loaded thing.  Fix in cvs.

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