Re: Prevent B c/B m from createing dups in target group

[Harry Putnam <reader@newsguy.com>]

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

> Harry Putnam <reader@newsguy.com> writes:
> 
> > With that warning mechanism in place, and provision to copy/move only
> > the unique messages on command, a user could simply throw a batch of
> > messages at a directory and only the unique stuff would stick...
> 
> Yeah.  But there is no predefined functionality in Gnus for doing
> this..

My OP was asking for an outline of how to go about starting to create
that functionality in gnus.  Once finished it could hopefully be
submitted for consideration as an inclusion.

I'm pretty sure once this kind of functionality became known it would
be seen as a nice addition.

>  and I think it sounds like something of a non-problem.  :-)

> When you suppress duplicate messages on group entry, you usually just
> see one copy in any case, no matter how many are actually there...

Possibly it is a non-problem but I see at least a few problems  with
that approach:

1) In the event I have edited the first copy in some way.  Then later
   looking back at old threads I see that same message not realizing
   I've already copied and edited it to a save group.  I copy it again
   but being in a hurry neglect to edit it.  Which one will show up
   when duplicate suppression on entry is engaged?

2) I run up on an old thread in a Newsgroup.  Maybe a discussion of
   `sender' and RFC provisions and decide I'd like to keep the whole
   thing...  all 235 : ) messages.  I've already piece meal saved 70,
   not necessaryily in order.  I just throw the whole batch into a
   saved group, now I have at least 70 dups.  Do I want that overhead?
   When I might possible be able to write something for gnus that
   would allow me to do that and only actually move the unique ones on
   my request.

3) Suppression seems very much like taking pain pills to mask an
   injury while continuing to grind your body to dust...