From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Tue, 29 Mar 2011 09:26:25 +0200 [thread overview]
Message-ID: <ws8vvyidzy.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87ipv3i051.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 28 Mar 2011 19:13:30 +0100")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>>> Richard Riley <rileyrg@googlemail.com> writes:
>>>
>>> [...]
>>>
>>>> Just to re-iterate : I feel it makes sense to activate ALL subscribed
>>>> groups which are "agentised" since there is no network access
>>>
>>> Actually, I wouldn't want this. Offline, I often use a very slow laptop
>>> and it can take quite a while to activate all groups. I think changing
>>> the levels of the groups is easy enough, once we get past the
>>> distinction between native/foreign/secondary groups.
>>
>> Me too : a netbook with an n550. That said you understand my issue with
>> a "C u 5 g" type activation which forces re-reads from non agentised
>> groups? Potentially very expensive when facing roaming charges.
>
> yes, I understand your issue with this.
>
> what I don't understand is why, if I am using gnus *unplugged*, doing
> "C-u 5 g" actually queries any online servers as opposed to querying the
> agent. This does seem to be wrong in some way... it doesn't bother me
> because when I'm offline, I am indeed *offline* and the queries time out
> immediately (with not cost incurred).
Gnus itself is never unplugged. Only certain servers... Heh ;) I think
there is an overlap between the meaning of the word "online" and
"activated". But I'm still not 100% sure .. and am certainly no closer
to being confident enough to offer docstring updates. As is usual with
Gnus I would bet a penny to a pound that there exists already the right
spell to make it work as I feel it should - its just a question of
someone with enough understanding of what it all means to explain it.
next prev parent reply other threads:[~2011-03-29 7:26 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
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 [this message]
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=ws8vvyidzy.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).