Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: nljlistbox2@gmail.com (N. Jackson)
To: info-gnus-english@gnu.org
Subject: How to stop Agent from fetching headers of uninteresting Groups?
Date: Tue, 14 Nov 2017 10:58:39 -0500	[thread overview]
Message-ID: <878tf8j1hs.fsf@moondust.localdomain> (raw)

I use the Agent for reading news offline (because I don't have an
Internet connection for many hours of the day). I only read a
handful of news groups offline, but the Agent downloads the
headers for every single group on my agentised servers. This takes
about fifteen or twenty minutes every time I do `J s' because I
have very many groups on those servers (most of which I only read
about once a year). Downloading the actual news for the groups I'm
interested in reading offline only takes about a minute, so it
seems insane to download all these headers that I don't want.

How can I tell the Agent to not download even the headers for a
group?

Currently I have one Agent category for each of my agentised
groups. That is the "default" category and it is set to 0 (by the
Agent when it first set itself up). For the groups I want to read
offline I have group parameters that tell the Agent to retrieve
all messages (I have a `true' predicate).

It seems I need an Agent predicate that is more strongly negative
than `false', something like `not-even-headers'.

I suppose I might be asking the wrong question, since the Agent
predicates are to tell the Agent which articles to get, it must
have already retrieved the unwanted headers before it even starts
applying the predicates. So I need a way of telling the Agent at a
higher level not to even get the headers. But I don't see anything
useful in the documentation.

What am I missing?

Thanks.

Regards,
N.





             reply	other threads:[~2017-11-14 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 15:58 N. Jackson [this message]
2017-11-30 21:57 ` Eric Abrahamsen
2017-12-07 14:55   ` N. Jackson
2017-12-07 17:13     ` Eric Abrahamsen
2017-12-11 18:08     ` N. Jackson

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=878tf8j1hs.fsf@moondust.localdomain \
    --to=nljlistbox2@gmail.com \
    --cc=info-gnus-english@gnu.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).