From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Agent not fetching headers in some groups
Date: Wed, 02 Apr 2003 20:57:18 -0600 [thread overview]
Message-ID: <u1y0kqodt.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <87brzq2bkr.fsf@ashar.iki.fi>
Jaakko Kangasharju <ashar@iki.fi> writes:
> I have had a problem with agent not fetching headers automatically for
> some groups for some time now. It is not more than a minor annoyance,
> but it would be nice to fix it somehow.
What version of Oort are you using?
> The problem is that when running 'J s' right after starting Gnus, it
> skips some groups, i.e. does not download headers or articles.
Just checking but have you agentized the group's server? Type '^' in
the group buffer to open the server buffer. Do you see '(agent)' next
to the server? If you don't, place point on the same line then type
'J a q'.
> But if
> I enter these groups in plugged mode, so that it fetches the headers,
> then after that 'J s' fetches the articles for those groups also. I
> have checked to the limit of my abilities the various files that the
> agent generates and I cannot see anything different compared to
> normally working groups.
Strange. One other user recently range into trouble by calling
(gnus-agentize) in the beginning of his config file rather than the
end. Make sure that everything has been configured first.
> If I run gnus-agent-regenerate in unplugged mode and right after press
> 'g', the article counts of these groups are all screwy, as if Gnus
> thought all the articles in these groups are unread. And entering any
> of these groups right after (still unplugged) shows a summary buffer
> with the indicated number of "Undownloaded article"s.
Kevin
next prev parent reply other threads:[~2003-04-03 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 20:43 Jaakko Kangasharju
2003-04-03 2:57 ` Kevin Greiner [this message]
2003-04-04 14:56 ` Jaakko Kangasharju
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=u1y0kqodt.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/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).