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: Re: How to stop Agent from fetching headers of uninteresting Groups?
Date: Thu, 07 Dec 2017 09:55:14 -0500	[thread overview]
Message-ID: <87374mmvu5.fsf@moondust.localdomain> (raw)
In-Reply-To: <87indrsa3m.fsf@ericabrahamsen.net>

At 13:57 -0800 on Thursday 2017-11-30, Eric Abrahamsen wrote:
>
> nljlistbox2@gmail.com (N. Jackson) writes:
>>
>> How can I tell the Agent to not download even the headers for a
>> group?
>>
>> It seems I need an Agent predicate that is more strongly
>> negative than `false', something like `not-even-headers'.
>
> I don't think it's possible to do this presently -- looking at
> `gnus-agent-fetch-group-1', the headers are indeed fetched
> before the predicate is examined. In principle, however, there's
> no reason why this wouldn't be possible: we could retrieve the
> predicate higher up in the function, and ignore the group
> altogether (unless some articles had been marked specifically
> for downloading).
>
> I suggest using `gnus-bug' to report this and describe the
> situation; hopefully someone will get to it!
>
> Eric

Hi Eric, thank you for the response.

Today I discovered `gnus-agent-handle-level' which I think I can
use to do what I want.

  gnus-agent-handle-level is a variable defined in
  `gnus-agent.el'. Its value is 5

  Documentation: Groups on levels higher than this variable will
  be ignored by the Agent.

  You can customize this variable.

All my news groups are currently at a subscribedness level of 3
(the default), so I'll bump up the subscribedness of the groups I
want the agent to retrieve anything for to level 2 and set
`gnus-agent-handle-level' to 2 as well. This should solve my
problem in a tidy way.

In fact, this seems to be such a natural solution that I'm not
sure that there is a need for a new feature, so I won't file a
feature request unless this plan doesn't work out for some reason.

N.




  reply	other threads:[~2017-12-07 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 15:58 N. Jackson
2017-11-30 21:57 ` Eric Abrahamsen
2017-12-07 14:55   ` N. Jackson [this message]
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=87374mmvu5.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).