From: Raja R Harinath <harinath@cs.umn.edu>
Subject: Gnus Supression: gnus-dup.el too aggressive?
Date: 13 Sep 1996 13:55:59 -0500 [thread overview]
Message-ID: <d9wwxy8csf.fsf@nebula.cs.umn.edu> (raw)
Hi,
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.
This has to be fixed. But how:
- should `gnus-dup' know about these message-ids, and ignore them. And,
which regexp to use: "\`none\+[^@]*\'" looks nice, is correct for mail
and "almost" correct for news.
- should Gnus maintain a dont-bother-saving list of message-ids. Looks
too heavyweight to me.
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.
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
next reply other threads:[~1996-09-13 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-13 18:55 Raja R Harinath [this message]
1996-09-18 1:04 ` Lars Magne Ingebrigtsen
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=d9wwxy8csf.fsf@nebula.cs.umn.edu \
--to=harinath@cs.umn.edu \
/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).