Re: nnir and move

[Ted Zlatanov <tzz@lifelogs.com>]

On Wed, 10 Nov 2010 11:40:37 -0500 Andrew Cohen <cohen@andy.bu.edu> wrote: 

>>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
AC> Oops, I think there is nothing to fix. The registry doesn't
AC> track where the message comes from but only where its going?
AC> Then there shouldn't be a problem...

Ted> Yeah.  Although in a move it needs to know the source so it can
Ted> delete that from the list of groups for the article.  So you'll
Ted> end up with stale knowledge in the registry.  I can
Ted> special-case nnir in the hooks or you can wrap the move in

Ted> (let ((gnus-original-source-group-for-move "xyz")) ...)

Ted> WDYT?  Ted


AC> I've done it with a let. I'll push a patch shortly.

AC> There is a another problem. nnir (intentionally) mangles the subject to
AC> add something like "[10:mail/3390] " at the front of the subject (this
AC> is [retrieval_score:real_group_name/real_article_number] ). Obviously we
AC> would like to remove it from the subject stored in the registry. I think
AC> the simplest solution would be to modify gnus-registry-simplify-subject
AC> to take care of it before it calls gnus-simplify-subject.

Could you use nnir-original-group and nnir-original-subject in the let
you said you would do?  I'll make the names more general if anyone else
needs it but I was thinking this way it's clear that it's a nnir
requirement.

That way the registry will not care what nnir does to the subject or
group name, it will just take the originals from the let-bound
variables.

Ted