Re: (provide 'nnmaildir)

[Simon Josefsson <simon@josefsson.org>]

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

> > > So... what conditions are article numbers supposed to satisfy?
> > 
> > They must be a positive elisp integer, and article numbers should be
> > persistant between gnus sessions.
> 
> So an article number for a particluar message must be constant for the
> life of that message... after a message expires, can its article
> number be reused?  My experiments indicate that nothing breaks
> violently, but Gnus remembers the readness of the article even after
> it expires, so a new article using the same number won't show up as
> new. :(

Yup.  Don't forget about the cache and the agent, they won't like two
articles having the same number.  So we have that Gnus article numbers
should be monotonously increasing, contigious and preferably start at
1.

> > >  What about nnoo-push-server?
> > 
> > I don't think you should use it.
> 
> What I saw in other backends was that nnoo-change-server was used in
> *-open-server, and nnoo-push-server was used everywhere else.  Should
> I use nnoo-change-server in all cases?

Gnus 5.8 doesn't seem to use nnoo-push-server at all, perhaps this has
changed.

> What about backend functions that don't take a defs argument?  How
> will they get the proper values of the backend variables for the
> current server?  Or is *-open-server always called first, if
> necessary, to make a server be current before calling another
> backend function?

I think so, yes.

> > > Why does gnus-nov-is-evil exist?
> > 
> > Some NNTP servers are broken wrt NOV.
> 
> So if my non-NNTP backend isn't broken, must I still obey it?

nnimap doesn't, but I'm not sure if anything gets hurt by this.