Make nnml primary server and nntp secondary server?

Make nnml primary server and nntp secondary server?

[Kai.Grossjohann]

I now have gnus-select-method pointed to my NNTP server, and
gnus-secondary-select-methods is ((nnml "")).

I'm thinking of switching these, i.e. set gnus-select-method to (nnml
"") and point gnus-secondary-select-methods to my NNTP server.

Problem is, I'm not sure why I want to do that :-)

I have the gut feeling that mail is much more important to me than
news, and thus mail shouldn't be `secondary'.  Also, I can quite well
imagine using Gnus for mail only.  And I think I don't want to always
type `nnml:' in front of mail groups...

What would be the implication of doing the change?  For instance, what
happens to M-x gnus-no-server RET?  Will it then connect to my NNTP
server and not bother with the nnml groups?

How could I go about changing this?  Of course, I want to keep the
.newsrc.eld stuff, so I think I must edit the .newsrc.eld...

Any suggestions welcome.

kai
-- 
Life is hard and then you die.

Re: Make nnml primary server and nntp secondary server?

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> What would be the implication of doing the change?  For instance, what
> happens to M-x gnus-no-server RET?  Will it then connect to my NNTP
> server and not bother with the nnml groups?

All backends are equal in the eyes of Gnus.  Gnus doesn't care whether 
the groups come from a mail backend or a Gnus backend, really.

And the only difference between primary and secondary servers is that
groups from the latter have nn*: prepended to the group names.  Kind
of.

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