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

[Harry Putnam <reader@newsguy.com>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > Some are whole threads that were copied a piece at a time as the
> > thread was developing.  Inevitabley there comes a point where you've
> > forgotten what has been copied and what not.  I found as many as four
> > layers of copies in some groups.  Partly due to absentmindedness but
> > also there is no built in functionality in gnus to prevent this.  Near
> > as I can tell.
> 
> You could also (setq gnus-use-cache t) and then tick the interesting
> messages.  Is there a specific reason for you not to do that?

Only as mentioned in previous post (not on server when you wrote
above) that it is handy to have a collection of messages under a topic
named group.  Far as I remember cacheing a message leaves it in its
original group, is that correct?  Or cacheing from NNTP groups, do
those go to a single directory?

> You say that you're editing messages.  What kind of editing is that?
> Surely, just putting them in the cache wouldn't be enough when you
> want to edit them.

Most often very light editing or none.  By light I mean adding a
keyword or two to Subject line or adding an entire new Keywords header.

Rarely a full body edit, but sometimes.

> But OTOH, why not allow editing of articles which are in the cache?
> That might be a useful feature.

Yeah and in conjuction with nnir could be used to create the cross
group summary buffer I'd like to have.  Assuming nnir can be aimed at
the cache.