Re: BUG REPORT tin 1.8.2 release 20060425 ("Shillay") [UNIX]
Urs Janßen <[email protected]>
| Newsgroups | gmane.network.tin.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Feb 02, 2007 at 01:56:48AM +0100, Mark-Oliver Wolter wrote:
> Version: tin 1.8.2 release 20060425 ("Shillay") Nov 29 2006 01:31:43
> tin running on spool
I didn't test this for ages :)
> cancel article
> article is still "there" when going to thread view and back to article view
cause it's internally cached (we could try to flush the cache in case of a
cancel, but it may not be worth the extra work).
> view another article
this 'flushes' the cache
> press - to go back to cancelled article
> 'Article unavailable'
correct behaviour so far
> However, the other article is now also marked unavailable.
this is a bug - present in 1.8.3 and 1.9.2 no matter if reading via nntp or
right from the spool.
> Reset by viewing even another article.
>
> Another thing: Since upgrading to this version (using the same configure flags
from which verson?
> as for the older version) followups in big threads won't post without manually
> shortening the References: header. Did I miss changes in the inews handling?
MAXREFSIZE (post.c) was increased from 512 to 998 in tin 1.7.4 (~ 3 years
ago). looks like your external inews can't handle such long lines. what
kind of newsserver do you use?
quick hack would be something like
#ifdef NNTP_ONLY
# define MAXREFSIZE 998
#else /* external inews might be limited */
# define MAXREFSIZE 512
#endif
in post.c ~line 2352
urs
--
"Only whimps use tape backup: _real_ men just upload their important stuff
on ftp, and let the rest of the world mirror it ;)" - Linus