From: William Henney <whenney@gmail.com>
To: Puneeth Chaganti <punchagan@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Announce] A GitHub Issues interface for Org-mode
Date: Mon, 30 May 2011 09:38:08 -0500 [thread overview]
Message-ID: <BANLkTimBZNKJXO0K_MC1s3_1oWeOOTM+=A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimf2Lg-AwsuQ75OCOUDBGYbNf9ugw@mail.gmail.com>
Hi Puneeth
On Sun, May 29, 2011 at 11:43 PM, Puneeth Chaganti <punchagan@gmail.com> wrote:
> 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 <whenney@gmail.com> 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. I 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 =org-ghi-update-current-issue=. 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
--
Dr William Henney, Centro de Radioastronomía y Astrofísica,
Universidad Nacional Autónoma de México, Campus Morelia
next prev parent reply other threads:[~2011-05-30 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 4:40 [Announce] A GitHub Issues interface for Org-mode Puneeth Chaganti
2011-05-30 3:46 ` William Henney
2011-05-30 4:43 ` Puneeth Chaganti
2011-05-30 14:38 ` William Henney [this message]
2011-06-02 0:41 ` Puneeth Chaganti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTimBZNKJXO0K_MC1s3_1oWeOOTM+=A@mail.gmail.com' \
--to=whenney@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=punchagan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).