From: Helmut Eller <eller.helmut@gmail.com>
To: kawa@sourceware.org
Subject: Re: language server protocol for Kawa
Date: Sun, 14 Jan 2018 20:07:00 -0000 [thread overview]
Message-ID: <m2fu78uruv.fsf@caladan> (raw)
In-Reply-To: <78c36015-ce0d-a0cf-c81e-37f0ce4d8e9a@bothner.com>
On Fri, Jan 12 2018, Per Bothner wrote:
> Has anyone done any work for a Language Server Protocol
> (https://langserver.org/) for Kawa? Any insights or partial code?
Just some thoughts:
- For Kawa's Java code I'm using the Emacs lsp-mode as client and
Eclipse's jdt-server. While I wouldn't call that combo great, it
certainly helps navigating the code. (I'm still using make directly to
compile things.)
- It seems to me that an LSP server would like to have something like a
"project" file that lists the interesting source files, libraries etc.
I suppose plain Makefiles will not work so well for that; maybe Ant
files would work better. Or maybe Kawa should have something like
Rust's Cargo. My guess is that this will be an important design
decision.
Helmut
next prev parent reply other threads:[~2018-01-14 20:07 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
2018-01-14 20:07 ` Helmut Eller [this message]
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=m2fu78uruv.fsf@caladan \
--to=eller.helmut@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).