From: Per Bothner <per@bothner.com>
To: Helmut Eller <eller.helmut@gmail.com>, kawa@sourceware.org
Subject: Re: language server protocol for Kawa
Date: Sun, 14 Jan 2018 20:35:00 -0000 [thread overview]
Message-ID: <bee782ba-5231-6f29-4da1-d84b855b9390@bothner.com> (raw)
In-Reply-To: <m2fu78uruv.fsf@caladan>
On 01/14/2018 12:07 PM, Helmut Eller wrote:
> - 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.
Definitely things to ponder and research, which I have barely started on.
I would like to have good defaults, so at least basic syntax checking
(and syntax coloring) works even without a project file. That is one
of the things I like about Emacs - you can edit a file without having
create a project containing the file.
I'd also like the server to be able to use import, module-name,
require, and define-library forms to find definitions.
However, in general one will want some kind of project file - for
example for compiler options or adding jar files to a classpath.
This is something I will need to study other servers for.
Scanning a Makefile for project properties doesn't seem like
it would be difficult - at least string-valued properties.
The Makefiles would have to follow certain conventions, just
like automake source files already do.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2018-01-14 20:35 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
2018-01-14 20:35 ` Per Bothner [this message]
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=bee782ba-5231-6f29-4da1-d84b855b9390@bothner.com \
--to=per@bothner.com \
--cc=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).