Re: What's needed for mutt 1.6?
Hi, Rocco Rutte!
Sometime (on Tuesday, February 27 at 19:45) I've received something...
>* Andriy N. Gritsenko [07-02-27 12:48:12 +0200] wrote:
>>Sorry. So I think we can add optional NNTP support into current
>>tree and move it into plug-in when time comes. :)
>What NNTP patch are you talking about?
>I known only vvv.nntp a little and I'd vote against it. The problem is
>that it hacks up mutt with tons of #ifdef, doesn't (yet?) integragte
>with hcache and message cache but rolls its own caching mechanisms based
>on news overviews without encoding information. It contains code with
>predictable tempfiles, etc.
I'm talking about that one. It was written in 1998-1999 years by me
when much of recent features weren't in the Mutt yet. Since nobody of
maintainers were interested in including NNTP support into Mutt, I've
dropped developing of it and Vsevolod take it, mostly porting the patch
to newest versions of Mutt. #ifdef's are there for simple reason to not
add code when configure script is called without --enable-nntp.
>If you ask me, including a patch is easy, but someone actually has to
>clean it up. I'm more conservative and prefer cleaning patches up before
>including them because this way there's at least some motivation for the
>developer(s) left.
If there is a positive willing to include NNTP support into Mutt then
I may clean it up and then I'll ask you to tell me which things do not
satisfy you beside noted above. :)
>I once started some really simple and early work for a simple pluggable
>mailbox driver system. Once done, it could be easily extended to allow
>for any type of filter (compressed folder) and to allow for more mailbox
>drivers implementing the interface (NNTP). But this is quite difficult
>and long way to go since the code is so closely coupled already... :(
I understand how difficult it is. :(
With best wishes.
Andriy.