Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@jhu.edu>
Subject: expiry in virtual groups
Date: Wed, 12 Jan 2000 02:26:49 -0500	[thread overview]
Message-ID: <87vh4zzr5y.fsf@chow.mat.jhu.edu> (raw)

I have two groups nnfolder:Inbox and nnfolder:Sent, and a virtual
group nnvirtual:Both which encompasses the previous two.  None of the
groups use total-expire or auto-expire;  I manually mark articles with
`E'.  When gnus-group-expire-all-groups is run, or when
gnus-group-expire-articles is run on the virtual group, the E mark
disappears from all articles in the two component groups which were
marked as expirable, but which weren't old enough to be deleted.  Old
expirable articles are deleted as they should be.

This didn't happen until recently.  I am currently running gnus
from cvs.  The latest lisp/Changelog entry is dated 2000-01-09 22:52:35.
My previous gnus version was probably a few weeks old.

Any idea how to fix this?

Dan

-- 
Dan Christensen
jdc@math.jhu.edu



             reply	other threads:[~2000-01-12  7:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-12  7:26 Dan Christensen [this message]
2000-04-21 13:25 ` Lars Magne Ingebrigtsen
2000-04-24 17:51   ` Dan Christensen
2000-08-10 19:19     ` Lars Magne Ingebrigtsen
2000-08-10 19:28       ` Paul Jarc
2000-08-10 19:41         ` Lars Magne Ingebrigtsen
2000-09-04  3:57           ` Paul Jarc
2000-09-09 18:19           ` Dan Christensen
  -- strict thread matches above, loose matches on Subject: below --
1999-04-14 23:54 Expiry " Hrvoje Niksic
1999-04-17  8:08 ` Lars Magne Ingebrigtsen
1999-04-17 16:22   ` Hrvoje Niksic
1999-04-17 16:53     ` Lars Magne Ingebrigtsen
1999-04-18 17:51       ` Hrvoje Niksic
1999-04-18 18:29         ` Lars Magne Ingebrigtsen
1999-04-19 12:30           ` Hrvoje Niksic
1999-06-12  2:04             ` Lars Magne Ingebrigtsen
1999-04-17 19:35     ` Matt Pharr
1999-04-19 14:34     ` Justin Sheehy
1999-04-19 16:06       ` Stainless Steel Rat

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=87vh4zzr5y.fsf@chow.mat.jhu.edu \
    --to=jdc@jhu.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).