From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Cc: ding@ifi.uio.no
Subject: Re: Gnus Supression: gnus-dup.el too aggressive?
Date: 18 Sep 1996 03:04:39 +0200 [thread overview]
Message-ID: <x67mpsws48.fsf@eyesore.no> (raw)
In-Reply-To: Raja R Harinath's message of 13 Sep 1996 13:55:59 -0500
Raja R Harinath <harinath@cs.umn.edu> writes:
> I have `gnus-supress-duplicates', and `gnus-save-duplicates-list'. The
> problem is that it supresses articles in most nndoc generated digests
> group (C-d). I figured out why: Gnus allots a emacs-session-time unique
> id to each message without an id, "none+nnn". This ID gets saved in the
> duplicates list across Emacsen and wrongly supresses most of newly
> generated temporary articles.
Right. I think nndoc should create better Message-IDs. I've put this
on the Red Gnus todo list.
> By the way, in `gnus-dup-enter-articles', message-ids should probably be
> checked if already in the list (intern-soft message-id gnus-dup-hashtb)
> before entering into the `gnus-dup-list'. This prevents duplicates in
> the duplicates list.
:-) Fix in Red Gnus v0.38.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-09-18 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-13 18:55 Raja R Harinath
1996-09-18 1:04 ` Lars Magne Ingebrigtsen [this message]
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=x67mpsws48.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
--cc=ding@ifi.uio.no \
/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).