| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The rationale behind this is to make boundaries clearer as mason.nvim
has no direct relation with lspconfig per se.
Also, hopefully, by having it as a separate package like this would
encourage more people to write similar extensions (think mason-dap and
mason-null-ls). Ideally such extensions wouldn't be required at all, but
there are definitely gaps to fill as of today.
From now on you'll need to add `williamboman/mason-lspconfig.nvim` as
a plugin if you want to use the `mason-lspconfig` extension:
```lua
use {
{ "williamboman/mason.nvim", branch = "alpha" },
"williamboman/mason-lspconfig.nvim",
"neovim/nvim-lspconfig",
}
```
```lua
Plug "williamboman/mason.nvim", { 'branch': 'alpha' }
Plug "williamboman/mason-lspconfig.nvim"
Plug "neovim/nvim-lspconfig"
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also make sure to exit neovim with an error exit code should one or more
installations fail.
|
| | |
|
| | |
|
| |
|
|
|
| |
* chore: update some logging
* docs: add section about known errors
|
| | |
|
| |
|
|
| |
All interactions from userland should preferably go through
require("nvim-lsp-installer").
|
| |
|
| |
Closes #752.
|
| | |
|
| |
|
|
|
|
| |
The ability to register custom servers still exist, it's just not
documented anymore. This will be reintroduced in some shape or form in
the future.
|
| |
|
| |
Closes #723.
|
| |
|
|
| |
(#716)
|
| |
|
| |
Closes #678.
|
| |
|
|
|
|
|
|
|
|
| |
automatic_installation
ensure_installed is used as a hard-coded list of servers to always
install, no matter if they're setup or not.
automatic_installation is used to automatically detect which servers
needs to be installed, based on which servers are setup via lspconfig.
|
| | |
|
| |
|
|
|
| |
Fixes #658.
Closes #660.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
With the new setup structure, this is no longer relevant.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* feat: integrate with lspconfig's on_setup hook
* fix!: don't use aliased installation directories if new .setup() fn is used
This makes it so servers are always installed in a directory name that
corresponds with the server name. The reason aliased installation directories
is supported is lost on me, but it's legacy and complicates things
unnecessarily.
This is a breaking change for users who previously were using the `.on_server_ready()`
hook, and now transitioned to setting up servers directly via lspconfig.
These users will need to reinstall the server.
* fix: block usage of the deprecated server:setup() method if new setup method is used
* fix: allow passing no arg to setup()
* docs: ok final.v3 readme
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
There wasn't much thought put into this snippet, it was just added as an
example of what one could do. The snippet happens to demonstrate how to
automatically install servers - this is however already documented (in a
different fashion) in the Wiki.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. This is a breaking change for the following servers, which will have to be
reinstalled:
- ltex
- clangd
2. This is a breaking change for users who reach into the default options (for
example via server:get_default_options()) to access the `cmd` property.
nvim-lsp-installer no longer provides the `cmd` (except in a few
instances), but instead provides an amended PATH which allows neovim's LSP
client to locate the locally installed executable.
To access the `cmd`, simply access it via lspconfig instead, for example
like so:
local default_config = require("lspconfig.server_configurations.rust_analyzer").default_config
print("I can now access the cmd governed by lspconfig:", default_config.cmd)
3. This is a breaking change for 3rd party use cases that makes use of the
`executable()` APIs (e.g., `npm.executable(root_dir, "tsserver")`). The
recommended usage is to instead to use the canonical name of the command
("tsserver"), while providing an amended PATH, for example:
local npm = require("nvim-lsp-installer.installers.npm")
local server = server.Server:new {
...,
root_dir = root_dir,
installer = npm.packages { "tsserver" },
default_options = {
cmd = { "tsserver" },
cmd_env = npm.env(root_dir),
}
}
|
| | |
|
| |
|
|
| |
This will prompt the user which server associated with the currently opened
buffer's &filetype to install.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Co-authored-by: William Boman <william@redwill.se>
|
| | |
|
