From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>
Cc: Kawa mailing list <kawa@sourceware.org>
Subject: Re: language server protocol for Kawa
Date: Sat, 13 Jan 2018 00:59:00 -0000 [thread overview]
Message-ID: <e433bd66-6875-bded-b849-9039078764e2@bothner.com> (raw)
In-Reply-To: <CABgWrqq6XHB_2sfDTvFieT=ggpK=KcXaKOYahO1xPZLZxqR8jw@mail.gmail.com>
On 01/12/2018 02:31 PM, Duncan Mak wrote:
> It was difficult to know if I'm making progress, because it seemed
> like all the things needed to come together all at the same time.
>
> If you're jumping into working on an LSP implementation, I'd love to
> contribute on GitLab if you can post issues with tasks for others to
> complete.
That's why I think I need to do at least a bare-bones implementation,
since I have the Kawa big-picture. Once I have *something* working,
then asking for help makes sense.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2018-01-13 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 22:04 Per Bothner
2018-01-12 22:32 ` Duncan Mak
2018-01-13 0:59 ` Per Bothner [this message]
2018-01-14 20:07 ` Helmut Eller
2018-01-14 20:35 ` Per Bothner
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=e433bd66-6875-bded-b849-9039078764e2@bothner.com \
--to=per@bothner.com \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).