Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: duplicate copies
Date: 14 Dec 1999 14:20:53 +1100	[thread overview]
Message-ID: <t4ivh628ay2.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Harry Putnam's message of "Mon, 13 Dec 1999 18:46:55 -0800"

>>>>> "Harry" == Harry Putnam <reader@newsguy.com> writes:

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

I would cache the required articles. (*). That way, duplicates
cannot occur.

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

I have seen the following variables:

gnus-suppress-duplicates
gnus-summary-ignore-duplicates
nnmail-treat-duplicates (set to delete).

At the moment I am confused at having 3 variables for the same
task. It is my guess:

- the top two only work within one group??? Or are they global
for all groups? Obviously, I am confused... What is the scope
for each of these variables?

- The first one marks duplicates with (M).
- The second hides duplicates so they aren't shown.
- the third one deletes the physical copy.

Can somebody please try to un-confuse me? I would really like
to know what these variables do.


For instance, lets say I wanted:

- duplicate messages within each group to be deleted (or not shown).

- duplicate messages between each group to be marked as read, but still
shown.

Is this possible?

(Note: I am assuming that the groups are mailing lists, hence Gnus
wont detect cross posts, at least with my current mail filtering
rules).

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

I think one of the above *might* help, but I would use the caching
feature instead.


-- 
Brian May <bmay@csse.monash.edu.au>


  reply	other threads:[~1999-12-14  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-14  2:46 Harry Putnam
1999-12-14  3:20 ` Brian May [this message]
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=t4ivh628ay2.fsf@silas-2.cc.monash.edu.au \
    --to=bmay@csse.monash.edu.au \
    /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).