From: "Adam Sjøgren" <asjo@koldfront.dk>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Wed, 20 Nov 2019 16:35:50 +0100 [thread overview]
Message-ID: <87mucqftm1.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87h82yvb7r.fsf@gmx.de> (Michael Albinus's message of "Wed, 20 Nov 2019 16:06:32 +0100")
Michael writes:
> Adam Sjøgren <asjo@koldfront.dk> writes:
>
>>>> Another thing I was thinking was that maybe nngitlab could build upon
>>>> the code in Magit Forge that already exists to talk to the APIs... but
>>>> given my level of familiarity with elisp, I might just start attempting
>>>> the simplest possible.
>>>
>>> Forge is tightly linked with Magit, calling magit-* functions.
>>
>> Ok, I was just hoping the interface to GitLab/Microsoft GitHub/etc. was
>> separated out and perhaps could be reused, but if not, so be it.
>
> These days I'm playing with Ghub, the working horse of Forge. Also from
> Jonas Bernoulli, also on melpa. Works fine for me.
Now I'm confused. Didn't you just say that the code Magit Forge uses to
talk to the various APIs is tightly linked with Magit?!
Best regards,
Adam
--
"I wish *I* was a tiger!" Adam Sjøgren
"A common lament." asjo@koldfront.dk
next prev parent reply other threads:[~2019-11-20 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 22:11 Adam Sjøgren
2019-11-20 3:31 ` Eric Abrahamsen
2019-11-20 4:12 ` dick.r.chiang
2019-11-20 11:33 ` Lars Ingebrigtsen
2019-11-20 12:38 ` Adam Sjøgren
[not found] ` <87h82ywu6i.fsf@gmx.de>
2019-11-20 15:01 ` Adam Sjøgren
[not found] ` <87h82yvb7r.fsf@gmx.de>
2019-11-20 15:35 ` Adam Sjøgren [this message]
2019-11-21 12:31 ` Lars Ingebrigtsen
2020-01-14 20:42 ` Adam Sjøgren
2020-01-14 21:23 ` dick
2020-01-14 22:03 ` Adam Sjøgren
2020-01-14 22:18 ` dick
2020-01-14 22:45 ` Adam Sjøgren
2020-01-15 4:47 ` dick
2020-03-17 11:03 ` dick.r.chiang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mucqftm1.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
--cc=michael.albinus@gmx.de \
/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.
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 NNTP newsgroup(s).