Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

it appears it's only possible to pull the opening text of an issue, no further updates #41

Open
nicferrier opened this issue Oct 25, 2014 · 1 comment

Comments

@nicferrier
Copy link
Contributor

This code:

(let ((ghcon (gh-issues-api "api")))
    (with-current-buffer (get-buffer-create "*marmalade-issues*")
      (erase-buffer)
      (--map
       (insert
        (format
         "#%s %s -- %s\n%s\n\n"
         (oref it number)
         (oref it created_at)
         (fill-string (oref it title))
         (fill-string (replace-regexp-in-string "\r" "\n" (oref it body)))))
       (oref
        (gh-issues-issue-list ghcon "nicferrier" "elmarmalade")
        data))
      (pop-to-buffer (current-buffer))))

Produces this currently:

#50 2014-10-24T09:41:37Z -- Issues with using marmalade
Hello, I am interested in getting some packages from marmalade for
emacs, but i can't seem to get it to work, whenever I try to access
the "http://marmalade-repo.org/packages/" URL I get "error in process
filter: could not create connection to marmalade-repo.org:433". Do i
need an account or something? Please help.

#47 2014-10-24T07:32:11Z -- eshell-manual is uninstallable
From marmalade#78



Seems to be related to version number?

#43 2014-10-18T12:47:25Z -- marmalade and discovery
Found this via #emacs 



http://vimawesome.com/



#30 2014-07-25T12:42:55Z -- Where's the searchbox?
I like the site redesign, but how do I search for packages now?

But I'd like to pull the updates too.

@sigma
Copy link
Owner

sigma commented Dec 30, 2014

so there seems to be some code for that in gh-pull-comments.el and gh-issues.comments.el

I've not been paying a lot of attention to those, and there seems to be a rather wide duplication of logic in there (especially considering that pull requests are really just another kind of issues, from a backend perspective). I might try to consolidate all this under proper "comments" objects, but in the meantime it might give you what you want

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@sigma @nicferrier and others