Re: nnchoke-retrieve-groups and nnchoke-request-group

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Greg Stark <gsstark@mit.edu> writes:

> But that's not how it seems to work out. M-x gnus causes gnus to
> open the nntp server even though not a single nntp group is level 2
> or 3.

To avoid opening the servers, use `M-x gnus-no-server'.

> And C-u 4 g doesn't cause gnus to actually activate the level 3
> groups, or even open the nndsc server on which some of the level 4
> groups are.

Hm, yes...  The prefix to `g' doesn't affect foreign groups.  This
might be a bug.  Should I change this?

> Furthermore, if i have gnus-read-active-file set to 'some then gnus
> reads active file information on all the groups level 7 and below it
> just throws that information away.

It's not thrown away, I think; it's just not used for much.

> It's somewhat unfortunate that M-g doesn't sound like it will ever be able to
> do what i want (batch all the groups into a retrieve-groups style request).
> I'm not really concerned with the semantic difference between the two queries
> that sounds nntp-specific, that the active file can differ and be out of date
> compared to the request-group query information.

It's up to the backend, of course, but the idea is that `M-g', should
report a "thorough" answer while `-request-list' should give a "fast"
answer. 

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