languagetool-language-server / languagetool-languageserver

LanguageTool language server to add grammar checking support to editors and other tools that use the Language Server Protocol (LSP)
Mozilla Public License 2.0
55 stars 4 forks source link

Install instructions #1

Open seba-1511 opened 7 years ago

seba-1511 commented 7 years ago

This project looks quite promising, especially given that most editors are including support for LSP.

Could you provide install instructions for people that are not familiar with gradle/the java ecosystem ?

Thanks, Séb

adamvoss commented 7 years ago

Are you looking for build instructions or installation instructions?

Build instructions I can do: gradle build

Installation instructions would become a matter of what you mean by "install." Currently the only client I know of is vscode-languagetool which bundles this server so separate installation is not required.

seba-1511 commented 7 years ago

Thanks for your quick reply.

I managed to run gradle build, but how would I start the language server ? (e.g. for python I would start it with pyls , for C clangd, etc...)

My specific language client is for neovim, but I assume this would be useful for others too.

adamvoss commented 7 years ago

Here is how you can start this application:

gradle installDist
./build/install/languagetool-languageserver/bin/languagetool-languageserver $PORT_NUMBER

Where $PORT_NUMBER is the port for the socket connection (opened by the client) that the server will communicate with.


I'll be happy to accept pull requests that add better support for other clients, but this is not something I will be undertaking myself in the foreseeable future. This does use LSP4J and speaks the protocol, but the actual communication piece was only written enough to support the VSCode client I was writing at the time.

plexigras commented 6 years ago

@seba-1511 did you get it to work?

seba-1511 commented 6 years ago

No, didn't have the time to fiddle and try to connect it with neovim-language-client.

davidlday commented 5 years ago

Please see issue #6.