unplugged-ness problem (fix?)

unplugged-ness problem (fix?)

[William M. Perry]

I think I've found the problem with the problem reported by a few people
last week about gnus-unplugged still trying to reach their remote servers.
I actually went and (gasp) read the manual and thought 'Hmmm... perhaps the 
servers are not agentized', so I went to the server buffer and tried to do
`J a', and got the error that ~/News/agent/lib/servers did not exist
(because ~/News/agent/lib did not exist).

Sooo, I created it, then tried to add the servers to the agent list again,
and got 'already agentized'.  So, removing them with `J r', then re-added
them, and all is working well now.

So, Gnus needs to:

a) create that directory if it doesn't exist (in gnus-agentize I guess)
b) Even if it doesn't exist it evidently still thinks the groups are
   agentized, but then doesn't _really_ act like they are.

Lars, does this give you enough ammunition to go bug hunting?

-Bill P.

Re: unplugged-ness problem (fix?)

[Lars Magne Ingebrigtsen]

wmperry@aventail.com (William M. Perry) writes:

> a) create that directory if it doesn't exist (in gnus-agentize I guess)
> b) Even if it doesn't exist it evidently still thinks the groups are
>    agentized, but then doesn't _really_ act like they are.

I got a few patches that made the Agent create the directory a lot
more.  (These are in 0.69.)  Does this fix the problem?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen