Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: I want to expire some even if unread
Date: Sat, 13 Jun 2020 14:42:31 -0700	[thread overview]
Message-ID: <87lfkqej7c.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <s0er1uiivrd.fsf@gmail.com>

David Rogers <davidandrewrogers@gmail.com> writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Saturday, 13 Jun 2020 at 02:35, davidandrewrogers@gmail.com
>> wrote:
>>> The manual states more than once that
>>> gnus-auto-expirable-newsgroups
>>> only expires messages that have been read; my question is about
>>> expiring *all* messages, even the unread ones, when they get old.
>>> If
>>> gnus-auto-expirable-newsgroups can be made to expire both read and
>>> unread together, then that's great. (but please tell me how)
>>
>> I use "M H" and "M h" (selective catch-up, sorting the group by
>> date,
>> say) all the time to catch up many articles without reading them.
>> My
>> understanding is that these are then marked as having been read and,
>> with the setting that others have noted, will then participate in
>> the
>> expiry process.
>
> That makes sense. And the responses so far are tending to indicate to
> me that the answer to my question is essentially "No, Gnus won't do
> what you're asking about, try something different". Does that seem
> accurate? (since my question was specifically about deleting old
> unread messages automatically, with zero need for intervention)

Yes, in general Gnus tries very hard not to touch your unread messages.
There's `gnus-auto-expirable-marks', but of course you can't select for
_absence_ of a mark. As indicated by the other responses, your best bet
is probably just to make it more convenient/speedy to mark messages as
read.

Eric



  reply	other threads:[~2020-06-13 21:43 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
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 [this message]
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=87lfkqej7c.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).