From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: Agent Q
Date: Wed, 15 Dec 2010 00:58:39 +0100 [thread overview]
Message-ID: <czwrnb9aa8.fsf@news.eternal-september.org> (raw)
In-Reply-To: <m31v5kc69x.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 14 Dec 2010 23:56:58 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>>> `J s'.
>>
>> It doesnt get them. It only gets the headers.
>
> By default, it should get all articles (except the ones that are really
> long). And it does that for me.
use case example.
I enter a nntp group and tell it to fetch 2000 articles.
A while later I go "unplugged". I enter that group and the headers are
there. I select an article I havent previously read and it "marks it for
download". Its not getting the bodies. I cant see any setting in my
custom.el. Am I misunderstanding how it should work? If I am using agent
and am "plugged" it seems pointless not to default to getting the bodies
too.
>
>> Thats said, J s does refresh the groups (headers only) when plugged in
>> but "g" doesnt. Why is that? If we're plugged shouldnt "g" work as
>> before? Or is it just broken on my set up perhaps?
>
> It sounds really odd. If you're plugged, then `g' should, er, like
> update everything.
It updates nearly everything. I cant put my finger on what its not yet -
possibly ones with pending body downloads? I'll try and pinpoint it
further.
--
☘ http://www.shamrockirishbar.com, http://splash-of-open-sauce.blogspot.com/ http://www.richardriley.net
next prev parent reply other threads:[~2010-12-14 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 18:36 Richard Riley
2010-12-14 22:27 ` Lars Magne Ingebrigtsen
2010-12-14 22:54 ` Richard Riley
2010-12-14 22:56 ` Lars Magne Ingebrigtsen
2010-12-14 23:58 ` Richard Riley [this message]
2010-12-15 19:30 ` Lars Magne Ingebrigtsen
2010-12-16 19:26 ` Richard Riley
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=czwrnb9aa8.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.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).