Re: funny problems with nnmail-cache and split-fancy-with-parent

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

Josh Huber <huber@alum.wpi.edu> writes:

> Josh Huber <huber@alum.wpi.edu> writes:
>
>> Works for me, but after looking at this -- shouldn't there be a
>> better interface into nnmail-cache-insert?  We should go through and
>> find all the places which call it, which is only 10 places, and use
>> the optional argument for group name if possible.  checking for
>> bound symbols and using heuristics to get the group name seems a
>> little hackish to me ;) (no offense to Kai!)

No offense taken.  I now remember the feeling when writing the code.
It is not a pleasant memory :-)

> Of course, I spoke too soon here.  The reason this was done became
> apartent while looking at nnmail-check-duplication, which has no
> knowledge of the group.
>
> Perhaps something a little more generic for splitting could be done?
> bind gnus-current-split-group or something like that?

Yes.  Lars has said (years ago) that he just wants to define some
symbols which are bound and document them.

So why not do that now.  We need to find all places which call
nnmail-check-duplication, then frob them.  Alas, I now use nnimap
which doesn't use that code.  Any takers for testing it, at least?

> Perhaps we should just ignore it ;)
>
> What do you think about moving the priority of the symbol checking
> (the diff in the parent).

If it works for you, it's probably Good Stuff.

kai
-- 
Silence is foo!