Re: [PATCH]: Do not fetch nnrss url when unplugged

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

Xavier Maillard <zedek@gnu-rox.org> writes:

> Kevin Greiner <kgreiner <at> xpediantsolutions.com> writes:
>
>> 
>> Xavier Maillard <zedek <at> gnu-rox.org> writes:
>> 
>> > Hello,
>> >
>> > As discussed earlier this week, I had to "modify" nnrss.el to allow
>> > offline reading of nnrss feeds.
>> >
>> > The patch consists on checking 'gnus-plugged` value and if 't', let
>> > fetch-nnrss function fetch the url.
>> 
>> This patch is inappropriate.  The variable gnus-plugged should not be
>> visible to the backends.  Looking back at your previous thread, I
>
> Oups. I didn't know about that. What is the appropriate way to achieve this task
> then ? I don't see anything about agent in 'nnrss.el'.

The agent is part of the gnus internals so a backend shouldn't need to
directly reference it.

>> don't know why you are unable to agentize your nnrss backend.  Can you
>
> In fact when agentizing (ie adding it to the agent), it works partially. But
> whenever you try to deagentize it, it fails with an error telling you this was
> not handled by the agent.

Right now, I don't know whether the agentize server (J a) failed (in
which case the J r should fail) or the remove agentized server (J r)
is failing as you indicated.  Does 'J a' update the server buffer to
display '(agent)' after the nnrss server's name?

Would you mind doing some lite debugging?  I'd like to know the value
of named-server in both gnus-agent-add-server and
gnus-agent-remove-server.

Kevin