Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: duplicate copies
Date: 13 Dec 1999 18:46:55 -0800	[thread overview]
Message-ID: <m3g0x6b5nk.fsf@satellite.local.lan> (raw)


I often copy news messages to similar named nnml groups to hold for a
while, study, refer to or whatever.  I've never managed to figure out
how to avoid copying duplicates to a group.

Imagine you read a thread and you want to hold the messages awhile,
then a week later you see there are 10 new messsages in the thread but
in reading them you get mixed up as to which ones you already kept, So
end up copying some more than once.

Short of memory improvement classes ( way to late for that) how can
gnus help me out?  

There is quite a lot about dups in the manual but all seems very
complicated and hard to follow.

The ideal solution for  this problem exists in another news reader
whos name I cannot say outload, but its initials are "Forte Agent".

There the user can throw a handful of messages at a group and will be
prompted as to whether they really want dups.  If you say "no" then the
ones that are dups don't get moved.  A handy way to sort it out.

Can gnus do something like that?



             reply	other threads:[~1999-12-14  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-14  2:46 Harry Putnam [this message]
1999-12-14  3:20 ` Brian May
1999-12-21 20:29 ` Kai Großjohann
1999-12-22 10:37   ` Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3g0x6b5nk.fsf@satellite.local.lan \
    --to=reader@newsguy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).