Re: Gnus backend for GitHub/GitLab?

["Adam Sjøgren" <asjo@koldfront.dk>]

dick writes:

> AS> As far as I can see, these need to be mapped to article numbers, so Gnus
> AS> can get information about max number and min number for the group, and to
> AS> retrieve articles by number.
>
> Yes, absolutely, your backend needs to sequentially number articles (which in
> this context are issues/comments).
>
> But that numbering is one of your own making, not gitlab's.

Yes, that's pretty much exactly what I wrote.

> I keep an array of articles (to go from our numbering to the issue/comment).
> And I maintain a hashtable to go from gitlab's arbitrary id to our numbering.

It sounds like you've already implemented nngitlab, is this something
you care to share?

> Is there a requirement to keep no state?

I would prefer the backend only depend on the API - and of course Gnus
will do whatever it usually does with state.

> I need to at least persist state for .newsrc.eld to keep track of what
> has and hasn't been read and seen (yes, there's a difference in Gnus
> between "read" and "seen").

This is something Gnus keeps track of generally, not something that a
new backend needs to concern itself with, right?

So besides what Gnus usually does, you keep state about your mapping
between GitLab's ids and article numbers - where do you keep that state,
inside .newsrc.eld or in a separate file?


  Best regards,

    Adam

-- 
 "What would you like to drink?" "Formaldehyde."            Adam Sjøgren
 "Straight or on the rocks?"                           asjo@koldfront.dk