Thomas Frössman

It's only the link headers that reveals where the last page is though without resorting to some trial and "error" method. It's the same for all paged api resources except...

All Gitlab API REST resource endpoints uses the link headers.. I don't understand what your comment about org files has any connection to this issue, however I am also only...

Alright.. In that case my suggestion is still to loop inside the get request\* functions in gitlab-util that fetches all results, possibly in combination with defining an variable that makes...

The alternative to always looping for all results is to introduce paging into the elisp gitlab API but I cannot see much reason for this.. I don't think there is...

I've just wrote some basic code to generate org tables for my issues in projects.. Was thinking about filtering.. I'm short on time so I did not try to debug...

Unrelated to this issue but.. I did this last week, Just the bare minimun that I need to easy my working day.. It's a one way sync just running a...

Yeah.. what I have is currently only what I'm pasting below... I have never work with org mode directly in this way before so I am still learning how to...

Using intermediate containers in builds also creates problems since `docker image prune` will just delete them since they have not tag associated. For some applications I have started using docker...

After further research I have decided that I'm personally only interested in the defMON sync interface and since that uses the user port it's probably better to just build myself...

it is confusing though, on the same page sid socket detected also uses the same grayed out decoration to display a detected value which is why I intuitively expected the...