Re: a few questions about the agent

[Matt Pharr <mmp@Graphics.Stanford.EDU>]

Harry Putnam <reader@newsguy.com> writes:
> Matt Pharr <mmp@Graphics.Stanford.EDU> writes:
> > 
> > I'm having this problem, too--I'm using slrnpull to handle news (thanks to
> > Kai (I think) and Jean-Albert Ferrez for tips on the slrnpull/rsync combo),
> > and so I don't want the agent to worry about any article management--I just
> > want the functionality of the queueing stuff for mail/news that I send when 
> > I'm unplugged.
> > 
> > However, each time I start up gnus-unplugged, I need to go into the server
> > buffer and J r my nnspool server--somehow it doesn't ever seem to remember
> > that I've J r'd it before.  Any ideas?  Where does gnus store the info
> > about which servers the agent is going to pay attention to, anyway?
> 
> News/agent/lib/servers
> 
> They only show up there if you've `J a'ed something besides the default
> gnus-select-method.... I think.

Aha.

So agent/lib/servers has just 'nil' in it, as I'd expect.  However, I
notice that gnus-agentize has the following code in it:

  (unless gnus-agent-covered-methods
    (setq gnus-agent-covered-methods (list gnus-select-method))))

which explains why it keeps thinking that it wants to agentize my nnspool:
server.  Why should it be doing this?  I suggest that it's a bug, though
assume that there's some reason for it to have been added.  Maybe the
intent was so that the first time the agent is started it makes a
reasonable guess for what to agentize?

I've 'fixed' this by just setting gnus-agent-covered-methods to nil right
after I (gnus-agentize) in my .gnus.el, but this seems like it shouldn't be 
necessary...

-matt
-- 
Matt Pharr                                   mmp@graphics.stanford.edu
<URL:http://graphics.stanford.edu/~mmp>