From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Tue, 29 Mar 2011 18:06:23 +0100 [thread overview]
Message-ID: <87k4fh26wg.fsf@ucl.ac.uk> (raw)
In-Reply-To: <ws8vvyidzy.fsf@news.eternal-september.org> (Richard Riley's message of "Tue, 29 Mar 2011 09:26:25 +0200")
Richard Riley <rileyrg@googlemail.com> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>> 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 ;)
Ah ha. You are correct. My confusion came from the inconsistency in the
documentation. E.g.:
,----
| J j runs the command gnus-agent-toggle-plugged, which is an |
| interactive compiled Lisp function in `gnus-agent.el'. |
| |
| It is bound to J j, <menu-bar> <Agent> <Toggle plugged>. |
| |
| (gnus-agent-toggle-plugged SET-TO) |
| |
| Toggle whether Gnus is unplugged or not. |
`----
Note the last line. However, in the info manual,
,----
| Gnus is never really in plugged or unplugged state. Rather, it
| applies that state to each server individually. This means that some
| servers can be plugged while others can be unplugged. Additionally,
| some servers can be ignored by the Agent altogether (which means that
| they're kinda like plugged always).
|
| So when you unplug the Agent and then wonder why is Gnus opening a
| connection to the Net, the next step to do is to look whether all
| servers are agentized. If there is an unagentized server, you found
| the culprit.
`----
I guess this means that you need to agentise all servers to avoid
incurring costs while unplugged? Since in my case unplugged == "really
offline", I don't have your problem with costs...
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 + No Gnus v0.16
next prev parent reply other threads:[~2011-03-29 17:06 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
2011-03-29 17:06 ` Eric S Fraga [this message]
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=87k4fh26wg.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).