Re: Bugs in PGnus

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

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

> 1. Pushing A R doesn't retrieve article numbers on my computer at
> Uni. However it works fine at Home, with the same configuration,
> except for a different news server (one that I administrate) and a
> different .newsrc.eld file. (Lars implied that this shouldn't work at
> all - weird - or perhaps I misunderstood him?). Perhaps the news server
> here is giving bad index files or something - I don't particularly
> trust it.  It would be good if I could be more specific though, when
> complaining to the administrator...

Have you tried setting nntp-record-commands to t, then compare traces
of the communication between Gnus and the NNTP server at uni and at
home?

> 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.
> 
> (I suspect this is only part of the threading problem, but I can
> reproduce this bug... From memory I get similar problems without
> pushing "Y c" but haven't yet reproduced it "on demand").

I also see this problem.  Hm.  But I use `/ *' rather than `Y c'.  Is
the behavior different?  Why are there two commands?

> 3. I get lots of ~/Mail/Incoming* files, which never seem to be
> deleted.  Perhaps this is to keep a backup in case things go wrong,
> however I already do that via my .forward file. 

See mail-source-delete-incoming.  This is indeed a safety net because
this is an alpha version of Gnus.

kai
-- 
because I couldn't think of a good beginning.