Gnus development mailing list
 help / color / mirror / Atom feed
From: soma@cs.unm.edu (Anil B. Somayaji)
Subject: crossposted mail articles not expired?
Date: 18 Dec 1998 09:52:31 -0700	[thread overview]
Message-ID: <ut21zlxl7e8.fsf@lydia.adaptive.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

Hello!  There's a little "feature" that has been bugging me for a little
while now.  I have lots of nnml groups, and my split rules often
result in crossposts.  This all works fine, and in fact I love it.
Unfortunately, when I have an article expire in one group, it remains
present in the other crossposted groups.  Even worse, the article now
has Xref lines referring to non-existent files (hard links, really).

Here's a real example.  I have a message that was crossposted between my
"adaptive" and "forrest" directories.  In the header, it has:

  Xref: atropos.cs.unm.edu forrest:1000 adaptive:276

However, I had marked the article for expiration in the adaptive
group, and so adaptive:276 no longer exists.  But forrest:1000 does,
with the reference to adaptive:276!

Perhaps it should be an option, but it would be nice if gnus
automatically expired all copies of an article.  Or, maybe when you
manually mark an article for expiration (which is all I do - I'm a
pack rat), there would be a command for "mark to expire this article
and all of its crosspostings."  And, if this is not done, maybe the
bogus Xref should be removed.

I'd be happy to hack on this, if someone can point me to the relevant
functions - I haven't studied the gnus source much.

BTW, I'm running pgnus 0.66.  Thanks!

  --Anil

-- 
Anil Somayaji (soma@cs.unm.edu)
http://www.cs.unm.edu/~soma
+1 505 872 3150

[-- Attachment #2: Type: application/pgp-signature, Size: 284 bytes --]

             reply	other threads:[~1998-12-18 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-18 16:52 Anil B. Somayaji [this message]
1998-12-18 17:48 ` Graham Murray
1998-12-18 18:08   ` Anil B. Somayaji
1998-12-20  6:49     ` Yair Friedman
1998-12-18 21:29   ` Matt Armstrong
1998-12-19  1:16 ` Kai.Grossjohann

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=ut21zlxl7e8.fsf@lydia.adaptive.net \
    --to=soma@cs.unm.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).