From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Henney Subject: Re: [Announce] A GitHub Issues interface for Org-mode Date: Mon, 30 May 2011 09:38:08 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:46483) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QR3bf-0001pw-5q for emacs-orgmode@gnu.org; Mon, 30 May 2011 10:38:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QR3be-00043O-02 for emacs-orgmode@gnu.org; Mon, 30 May 2011 10:38:11 -0400 Received: from mail-bw0-f41.google.com ([209.85.214.41]:35509) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QR3bd-00043H-FL for emacs-orgmode@gnu.org; Mon, 30 May 2011 10:38:09 -0400 Received: by bwz17 with SMTP id 17so3649174bwz.0 for ; Mon, 30 May 2011 07:38:08 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Puneeth Chaganti Cc: emacs-orgmode Hi Puneeth On Sun, May 29, 2011 at 11:43 PM, Puneeth Chaganti wr= ote: > William, > > Thanks for trying it out! > No problem - anything to avoid doing my real work.... > On Mon, May 30, 2011 at 9:16 AM, William Henney wrote= : >> >> This looks very promising - thanks! It is a shame though that the body >> of the issue and the comments don't get synched (I see that you have >> these listed as TODO). I also noticed that if I type any text directly > > This is Experimental and I am open to suggestions, but one of the > problems I have is that the GitHub API v3 is unstable and causing some > trouble. I initially had a version, where the BODY of the issue was > being sync-ed, but after a while, I stopped getting the body of the > issue in the JSON. I'm not sure what went wrong, but a simple GET > using curl also failed to give me the body. =A0I shall look at it again, > in a short while. > Is the v2 API missing some features you need? Maybe it would be better to use that until v3 is out of beta > >> under the issue's heading in my org file, then this text is /wiped/ >> when I execute =3Dorg-ghi-update-current-issue=3D. However, any >> subheadings (and their text) do survive, but they never get synched >> back to GitHub. > > I haven't figured out what would be the right way to do this. I am > open to any suggestions from your side. > Well, the wiping of text directly below an issue's level 2 heading is a data-loss bug, so I would suggest that you certainly don't do that :) With respect to sub-headings (level 3 or below) that are added by hand to the github.org file, I would suggest that by default you do not sync them with GitHub. Maybe you could have a function called something like org-ghi-make-heading-a-comment that would work in a similar way to org-ghi-make-todo-an-issue. However, it seems that GitHub issue comments only understand markdown syntax, not org syntax, so unless the comment is just simple text it would require an export step (https://github.com/alexhenning/ORGMODE-Markdown might help there). Cheers Will --=20 =A0 Dr William Henney, Centro de Radioastronom=EDa y Astrof=EDsica, =A0 Universidad Nacional Aut=F3noma de M=E9xico, Campus Morelia