Re: Aget woes in oort gnus

[Kinkie <REAL-ADDRESS-IN-SIGNATURE@kinkie.it>]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

[...]

>>>> - with 0.15 I had this problem where despite being started as
>>>> gnus-unplugged, it complained that it couldn't select my
>>>> gnus-select-method server at startup. Having it denied, going to the
>>>> server buffer, re-enabling it and gnus-group-get-new-news'ing would
>>>> allow me to see the groups from that server. I'm not sure this is
>>>> still true (I've just updated).
>>>
>>> Pls retest.  This should have been fixed in revision 6.151.
>>
>> Gnus behaved as I described in the run I'm writing this article with,
>> which is today's CVS HEAD.
>>
> OK, two out of three isn't bad.
>
> BTW, expiration can be painfully slow.  I just checked in a couple of
> very minor changes that should make it a little faster.

It's OK for me. I only follow 30something groups, not more than 1k
articles/day.

> I've been unable to reproduce the last error.  However, it sounds like
> your gnus-select-method server is no longer agentized.  I'd like you
> to check this by opening the server buffer ('^' in the group buffer).
> Your gnus-select-method server should display '(agent)' on the line
> next to its name.  If it does not, we've found the problem.  You can
> agentize that server by moving point to its name then typing 'J a'.

Already checked. It's agentized. Tried toggling it off and on, but no
changes.

-- 
	kinkie (kinkie-ml [at] tiscalinet [dot] it)
	Random fortune, unrelated to the message:
Virtue is a relative term.
		-- Spock, "Friday's Child", stardate 3499.1