From: David Rogers <davidandrewrogers@gmail.com>
To: Gnus mailing list <ding@gnus.org>
Subject: Re: I want to expire some even if unread
Date: Thu, 18 Jun 2020 16:03:56 -0700 [thread overview]
Message-ID: <s0ewo442cyr.fsf@gmail.com> (raw)
In-Reply-To: <874kre2lis.fsf@hillenius.net> (=?utf-8?Q?=22G=C4=B3s?= Hillenius"'s message of "Sun, 14 Jun 2020 08:45:31 +0200")
Gijs Hillenius <gijs@hillenius.net> writes:
> On 13 June 2020 13:28 David Rogers, wrote:
>
>> Gijs Hillenius <gijs@hillenius.net> writes:
>>
>>>> The manual states more than once that
>>>> gnus-auto-expirable-newsgroups
>>>
>>> Hm OK. But /mine/ says:
>>>
>>> Groups in which to automatically mark read articles as
>>> expirable.
>>
>> Exactly, that's what I said - I'm trying to automatically mark
>> UNread
>> articles as expirable (when they get old).
>
> doh! yes, oops you're right. It works because of the combination
> with
> gnus-topic-catchup-articles; which effectively marks all
> articles as
> read.
I've wondered about modifying a hook so that it will, just for my
chosen groups, automatically catch up to "x" days ago each time I
exit that group. Does that sound like a reasonable thing to try?
Or a dumb idea?
--
Thanks
David
next prev parent reply other threads:[~2020-06-18 23:05 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
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 [this message]
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=s0ewo442cyr.fsf@gmail.com \
--to=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).