Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Expiry in virtual groups
Date: 17 Apr 1999 18:22:00 +0200	[thread overview]
Message-ID: <87n2078bfb.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "17 Apr 1999 10:08:52 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> It is not the case.  Expiry is done from
> `gnus-summary-prepare-exit-hook' (which defaults to
> `gnus-summary-expire-articles').  The obvious kludge would be to
> have the latter function also expire component groups if the current
> group is a virtual group.

I don't think that would be a kludge, it's exactly the right solution.
If you feel it breaks the Gnus-vs-backends abstraction, you could make 
a way for backends to specify some sort of expiry parameters.

> But `gnus-summary-expire-articles' takes into account group props
> and stuff, and we don't want the group props from the virtual group
> to adhere to the component groups, do we?

We don't.  But then again, maybe it really /should/ be an
nnvirtual-specific kludge.

> Can't you just `C-c M-C-x' once in a while, like I do?  :-)

I can, but it's sort of yucky to have to do that.  I've never needed
to do it so far.


  reply	other threads:[~1999-04-17 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-14 23:54 Hrvoje Niksic
1999-04-17  8:08 ` Lars Magne Ingebrigtsen
1999-04-17 16:22   ` Hrvoje Niksic [this message]
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
2000-01-12  7:26 expiry " Dan Christensen
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

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=87n2078bfb.fsf@pc-hrvoje.srce.hr \
    --to=hniksic@srce.hr \
    /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).