-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation request: document how to install language server support #1893
Comments
I suppose we can also expand the output of |
All the information required has already been compiled here: https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md I had a quick go at extracting the default language servers used by Helix, removing the redundant information regarding the Neovim setup, and reformatting it. It would take quite a while to create the entire document, so please can I get some feedback if this would be useful. There is no point in duplicating the Neovim peoples' excellent work, but simply linking to the Neovim docs would make things far too complex and annoying. Most of it is not relevant to Helix users. Each link under LSP goes direct to the instructions, here is what I have so far as an example: how-to-install-default-language-servers.mdThe following are the default Helix language servers. To use them you must install them manually following the instructions below.
bashlshttps://github.com/mads-hartmann/bash-language-server
npm i -g bash-language-server Language server for bash, written using tree sitter in typescript. clangdhttps://clangd.llvm.org/installation.html NOTE: Clang >= 9 is recommended! See this issue for more. clangd relies on a JSON compilation database specified |
Ah, wonderful! I think a new Wiki page would be good for this so it's easy to compile and keep up to date gradually, and multiple people can contribute easily. Would you like to set this up @David-Else? What you have here looks like a good start. For the list of default language servers, we should link to https://docs.helix-editor.com/lang-support.html or point people towards |
@the-mikedavis Yes, I will sort it out. The Wiki has an automatic table of contents, so it should be easy for users to go straight to the language server they want to install. I will leave out the current table and point to the page you linked. I will credit the original Should this list of default language servers be for the latest release version of helix, or include language servers that may be in the master branch? (not that there are any at the moment, but I want to make that clear for people who might update the WIKI) I had a look at https://pkgs.org/search/?q=lsp and could not find many language servers of note. Did you have any in mind? I don't know much about brew or chocolatey, would there be advantages to using them if it were also on something like NPM? |
Oh hmm I suppose I'm a bit spoiled by Nix - it tends to have just about everything. Nixpkgs has rust-analyzer (here), as do the arch repos (here). If I look around for a less common LSP like For default language servers docs on the master branch: https://docs.helix-editor.com/master/lang-support.html (note the |
@the-mikedavis I have done it, https://github.com/helix-editor/helix/wiki/How-to-install-the-default-language-servers , what do you think? |
Looks great! Thanks for putting this all together @David-Else! |
How I thought it would work
I install Helix and LSP support would automatically be installed for me for supported languages.
Why I thought that
The output from the installation process makes it look like language support is being fetched and built for a number of languages. I didn’t see it mentioned that this does not include LSP/autocomplete support.
How it should work
I would still expect LSP support to be automatically installed for common languages. Barring that…
Suggested documentation
Autocomplete does not work by default in Helix as language servers are not automatically installed. Please follow the guides to install the language server for the supported languages:
e.g., TypeScript
Requires Node.js/npm (minimum version?)
The text was updated successfully, but these errors were encountered: