public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: gnu.expr.ModuleMethod no more? (+ Emacs SLIME)
Date: Mon, 05 Jun 2017 22:53:00 -0000	[thread overview]
Message-ID: <55e2bdcd-76fb-cefd-4367-2819f7436bde@bothner.com> (raw)
In-Reply-To: <CABgWrqoMrQ6ew0Rf9g2jXTDeVW9i4SQ7C3r-EK0+Ewn6Uo2J7A@mail.gmail.com>

On 06/05/2017 08:01 AM, Duncan Mak wrote:
> I'm interested in working on an LSP implementation for Kawa. Do you
> have any suggestions on how / where to get started?

One thing to do is look at other language servers, especially for
JVM-based languages: Groovy, Java, Scala, Clojure:
See https://github.com/Microsoft/language-server-protocol/wiki/Protocol-Implementations
https://github.com/thheller/shadow-cljs/issues/2

It seems plausible that when in a REPL we'd want to use the same
JVM for both the RPEL and the LSP server.  That leads to some interesting
possibilities and challenges integrating and editor with the REPL front-end.

> Adding support for ranges on top of positions seems like an obvious
> choice, but I'd also like to write more Scheme code than Java, do you
> know of any other tasks that would help get this feature bootstrapped?

I'm working on the basic data structure support for 'end positions'.
So far lots of compiler errors, but I'll check it in once there are
no regressions.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2017-06-05 22:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 20:50 Sudarshan S Chawathe
2017-06-05  0:29 ` Per Bothner
2017-06-05 13:34 ` Per Bothner
2017-06-05 15:01   ` Duncan Mak
2017-06-05 22:53     ` Per Bothner [this message]
2017-06-08 21:59     ` 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=55e2bdcd-76fb-cefd-4367-2819f7436bde@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).