Re: nnimap - not quite there yet?

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

prj@po.cwru.edu (Paul Jarc) writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > Gnus recognizes a secondary server by its presence in
>> gnus-secondary-select-methods.  The treatment of a secondary server
>> differs from a foreign server in that Gnus checks for new groups on
>> secondary servers, but not on foreign ones.
>
> WIBNI this behavior could be configured independently of how the
> server was created?

You can go to the server buffer and create a server nntp:foo.  Then
you can do (add-to-list 'gnus-secondary-select-methods "foo") to make
it secondary.

Is this what you want?

I wish this feature would use server names in the style of "nntp:foo",
like the rest of Gnus.  Oh, well...

>>> Example: I added an nntp group and set the level to 3.  My
>>> gnus-activate-level is set to 1.  When I run gnus-group-get-new-news
>>> this new group does not get queried.  That's what I'd like to have
>>> happen with my lower-level IMAP folders.
>> 
>> It's what should happen automatically.  If it doesn't happen, I think
>> that's a bug in nnimap.
>
> Backends don't know anything about levels.  Well, nnfoo-update-info
> has access to a group's level/rank, but that doesn't seem relevant
> here, and I imagine nnimap doesn't touch it anyway.

Hm.  Hmmm...

kai
-- 
~/.signature: No such file or directory