From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Fri, 25 Mar 2011 19:34:49 +0100 [thread overview]
Message-ID: <bsvcz7hwvq.fsf@news.eternal-september.org> (raw)
In-Reply-To: <fcd3lfw7ft.fsf@news.eternal-september.org> (Richard Riley's message of "Fri, 25 Mar 2011 16:23:02 +0100")
Richard Riley <rileyrg@googlemail.com> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>> That works yes! Wow. Thanks! But "foreign group"? Why are they foreign
>> groups? They are groups attached to nntp servers defined in select
>> methods. Ye gods its complicated ;) ...
>>
>
> I spoke too soon. Yes this "activates" the groups. But it also means
> they now, when plugged, fetch using the default "g" rather than when I
> specifically WANT these less important groups using something C-u 5
> g. Theres some kind of functionality overlap between plugged, activated
> and subscribed which seems to defeatt my use case.
>
> To reiterate
>
> I have some "higher level" levels for things like gaming nntp group for
> example. Lets say level 5. Imap and some others are at level 3.
>
> I set gnus-activate-level to 3.
>
> When "plugged" hitting "g" will now only fetch for level and below (its
> back to front IMO since more important groups have lower levels).This is
> great. If I want the advocacy wars etc in pc.gaming or whatever I hit
> C-u 5 g. Gnus then fetches this for me. But the important and correct
> thing is that it doesnt fetch the less important stuff using default
> "g". All fine.
>
> The problem however here is that when starting gnus *unplugged* these
> level 5 groups do not "activate" ie show the articles counts etc, even
> though its local. They *are* visible however since they are
> subscribed. IMO they should activate when unplugged.
>
> If I set the gnus-activate-foreign-newsgroups to 3 to activate them in
> unplugged by default then default "g" also fetches them. This is not
> desired behaviour when really roaming.
>
> Yes, when unplugged I *can* C-u 5 g to activate them, if their levels
> are 5, but this step should be unnecessary.
>
> I think this makes sense...
>
The above description of usage can be distilled to this suggestion:-
All groups *belonging to agentised servers* should be active when
unplugged regardless of their level. Not when plugged since otherwise
"g" will fetch for them - and this we do not want.
Does that make sense?
next prev parent reply other threads:[~2011-03-25 18:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 12:18 Richard Riley
2011-03-24 13:55 ` Eric S Fraga
2011-03-25 10:53 ` Richard Riley
2011-03-25 12:03 ` Eric S Fraga
2011-03-25 15:04 ` Richard Riley
2011-03-25 15:23 ` Richard Riley
2011-03-25 18:34 ` Richard Riley [this message]
2011-03-25 15:58 ` Eric S Fraga
2011-03-25 19:21 ` Adam Sjøgren
2011-03-25 21:05 ` Eric S Fraga
2011-03-25 21:13 ` Adam Sjøgren
2011-03-26 7:45 ` Richard Riley
2011-03-26 12:47 ` Adam Sjøgren
2011-03-27 7:15 ` Richard Riley
2011-03-27 7:25 ` Richard Riley
2011-03-27 17:38 ` Eric S Fraga
2011-03-28 15:03 ` Richard Riley
2011-03-28 17:07 ` Eric S Fraga
2011-03-28 16:33 ` Richard Riley
2011-03-28 18:13 ` Eric S Fraga
2011-03-29 7:26 ` Richard Riley
2011-03-29 17:06 ` Eric S Fraga
2011-03-26 7:43 ` 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=bsvcz7hwvq.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).