A recurring problem with multi-copies

A recurring problem with multi-copies

[Harry Putnam]

I've never fully understood all the variables related to handling
duplicate messages, there may well be some setting to handle this
recurring problem.  I could use some advice as to how to handle it.

Problem:

I sometimes copy messages to topic named (nnml) groups that I want
to keep for reference.  So sometimes a thread occurs in a newsgroup or
mail list group where I want to keep parts of the thread.  An example
might be in comp.lang.awk.  I post a message (query) and begin
recieving replies.

I copy the usefull replys to nnml:t.awk.   Three weeks later someone
who was on vacation replies to my query with really good or
controversial information.  Another round of replies start, many of
these I also want to keep but by now have forgotten what I kept and
what I didn't.

So I end up with a number of duplicates in nnml:t.awk

I'd like some built in (or add on) way where gnus would tell me that I
already have copies of the dup messages in `t.awk' group, and asks if
I want to copy them anyway... or something similar.

The best would be a situation where gnus would ask if I want to
continue copying and give me a choice of  only the unique messages or
dups and unique.

Re: A recurring problem with multi-copies

[Lars Magne Ingebrigtsen]

Harry Putnam <reader@newsguy.com> writes:

> I'd like some built in (or add on) way where gnus would tell me that I
> already have copies of the dup messages in `t.awk' group, and asks if
> I want to copy them anyway... or something similar.

I think that sounds too complex.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: A recurring problem with multi-copies

[Harry Putnam]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > I'd like some built in (or add on) way where gnus would tell me that I
> > already have copies of the dup messages in `t.awk' group, and asks if
> > I want to copy them anyway... or something similar.
> 
> I think that sounds too complex.

Just dealing with nnml for a moment, what would it really take?  The
nov file already contains the message-ids of those in the group.

Just guessing here, but could some kind of hook into `B c' `B m' call a
function that would scan the message-ids of the incoming messages, and
compare them to the existing nov info in target `nnml' group?

If that were done would it slow things down terribly?

Lets say a match occurs, immediately gnus spits out a message. 
`Some messages already present in TARGET group.. continue?
User hits `y' and gnus makes the move.  
User hits `n' and gnus only moves those messages whos ids *do not*
match the nov info.  Any matching message are left out.

This would be quite an enhancement for those of us who copy and move
stuff around extensively... and are senile and forgetful.