From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: two agent nits
Date: Mon, 01 Dec 2003 12:39:19 +0100 [thread overview]
Message-ID: <iluznec6a3c.fsf@latte.josefsson.org> (raw)
In-Reply-To: <u1xrp87pl.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Sun, 30 Nov 2003 22:47:50 -0600")
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> * I can't seem to get the agent to fetch read articles.
>> gnus-agent-consider-all-articles's value is t
>> The default agent category predicate is 'true'.
>> `J s' and `J u' just download unread or ticked articles.
>
> Have to tried setting gnus-agent-consider-all-articles to nil? That
> seems to work for me.
I tried, but still the same. Pressing `J u' on groups just say it is
finished, but only the unread/ticked articles are in my local cache.
Hm. The manual and the docstring for the variable doesn't seem to be
in sync. I thought the variable did what the docstring said, but the
manual just discuss missing headers. Which one is correct?
gnus-agent-consider-all-articles's value is t
If non-nil, consider also the read articles for downloading.
`gnus-agent-consider-all-articles'
If `gnus-agent-consider-all-articles' is non-`nil', the agent will
fetch all missing headers. When `nil', the agent will fetch only
new headers. The default is `nil'.
>> * The custom type of gnus-agent-expire-days is integer. What if I
>> don't want articles to be expired? Nil? 0? Either way, it should
>> be documented and the custom type improved.
>
> gnus-agent-expire-days is archiac (perhaps the documentation should
> say that) as it provides a global value. It used to provide a list of
> regular expressions matching group names but that didn't provide a
> visual interface for maintaining it. This use was deleted in 5.10 and
> replaced by agent parameters in categories, groups, and topics (See
> Agent Basics in the manual).
>
> If you want to globally turn expiration OFF, see
> gnus-agent-enable-expiration.
Ah, that variable is what I want. Thanks. I added a link in the
docstring in case others make the same mistake.
next prev parent reply other threads:[~2003-12-01 11:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 16:53 Simon Josefsson
2003-11-30 19:53 ` Harry Putnam
2003-11-30 20:18 ` Simon Josefsson
2003-12-01 3:13 ` Harry Putnam
2003-12-01 4:47 ` Kevin Greiner
2003-12-01 11:39 ` Simon Josefsson [this message]
2003-12-01 15:56 ` Kevin Greiner
2003-12-01 16:46 ` Simon Josefsson
2003-12-01 17:30 ` Kevin Greiner
2003-12-01 19:45 ` Simon Josefsson
2003-12-01 20:35 ` Harry Putnam
2003-12-02 3:02 ` Wes Hardaker
2003-12-02 6:01 ` Kevin Greiner
2003-12-02 17:40 ` Simon Josefsson
2003-12-03 21:47 ` Harry Putnam
2003-12-03 22:14 ` Simon Josefsson
2003-12-04 1:50 ` Harry Putnam
2003-12-04 2:29 ` Simon Josefsson
2003-12-04 5:54 ` Harry Putnam
2003-12-05 2:57 ` Harry Putnam
2003-12-05 3:25 ` Simon Josefsson
2003-12-05 3:54 ` Harry Putnam
2003-12-05 4:13 ` Simon Josefsson
2003-12-05 13:33 ` Harry Putnam
2003-12-02 20:35 ` Simon Josefsson
2003-12-02 22:28 ` Kevin Greiner
2003-12-01 12:30 ` Harry Putnam
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=iluznec6a3c.fsf@latte.josefsson.org \
--to=jas@extundo.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).