Gnus development mailing list
 help / color / mirror / Atom feed
From: "Gijs Hillenius" <gijs@hillenius.net>
To: David Rogers <davidandrewrogers@gmail.com>
Cc: Gnus list <ding@gnus.org>
Subject: Re: I want to expire some even if unread
Date: Sat, 13 Jun 2020 09:19:11 +0200	[thread overview]
Message-ID: <875zbv4emo.fsf@hillenius.net> (raw)
In-Reply-To: <s0ebllnkdio.fsf@gmail.com> (David Rogers's message of "Fri, 12 Jun 2020 17:36:31 -0700")

On 12 June 2020 17:36 David Rogers, wrote:

> Hello all
>
> I'm looking for a way, just on certain groups, to expire messages
> based ONLY on the fact that they're old, regardless of whether 
> they're read or not. I won't remember to activate a special switch
> every x weeks or whatever, so I'm looking for something I can "set 
> and forget". Perhaps this type of setup is considered too likely to
> cause unexpected data loss, but if I lose these particular groups by
> accident it won't really matter.
>
> Automatic catch-up to a certain point, maybe? I'm having a hard time
> finding information on this.
>
> It would be a nice bonus if ticked messages were kept, but I'd rather
> lose a few ticked messages than have no automatic expiry.

have you tried

gnus-auto-expirable-newsgroups

?



  reply	other threads:[~2020-06-13  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13  0:36 David Rogers
2020-06-13  7:19 ` Gijs Hillenius [this message]
2020-06-13  9:35   ` davidandrewrogers
2020-06-13  9:56     ` Gijs Hillenius
2020-06-13 16:26     ` Eric S Fraga
2020-06-13 19:57       ` David Rogers
2020-06-13 21:42         ` Eric Abrahamsen
2020-06-14  5:47           ` Andrew Cohen
     [not found]     ` <87pna32sq0.fsf@hillenius.net>
     [not found]       ` <s0ek10aiubj.fsf@gmail.com>
     [not found]         ` <874kre2lis.fsf@hillenius.net>
2020-06-18 23:03           ` David Rogers
2020-06-18 23:07           ` David Rogers

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=875zbv4emo.fsf@hillenius.net \
    --to=gijs@hillenius.net \
    --cc=davidandrewrogers@gmail.com \
    --cc=ding@gnus.org \
    /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).