From mboxrd@z Thu Jan 1 00:00:00 1970 From: Puneeth Chaganti Subject: Re: [Announce] A GitHub Issues interface for Org-mode Date: Thu, 2 Jun 2011 06:11:08 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:54843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRvye-0007kN-70 for emacs-orgmode@gnu.org; Wed, 01 Jun 2011 20:41:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRvyc-0001dA-6c for emacs-orgmode@gnu.org; Wed, 01 Jun 2011 20:41:31 -0400 Received: from mail-yi0-f41.google.com ([209.85.218.41]:62071) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRvyb-0001cT-E7 for emacs-orgmode@gnu.org; Wed, 01 Jun 2011 20:41:29 -0400 Received: by yib18 with SMTP id 18so197752yib.0 for ; Wed, 01 Jun 2011 17:41:28 -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: William Henney Cc: emacs-orgmode Hi William, On Mon, May 30, 2011 at 8:08 PM, William Henney wrote: [..] > Is the v2 API missing some features you need? Maybe it would be better > to use that until v3 is out of beta v2 API doesn't provide access to the new features of Issues, added in version 2 of GitHub Issues, like Milestones. I thought adding the Milestone due date as a deadline would be useful. But, as you suggest, I should probably try things with APIv2 until the v3 is more stable. [..] > 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 > :) Yes. I'll fix it, as soon as I get some time and am able to move stuff to v2. > 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). Thanks for the suggestions, will look into them. :) -- Puneeth