| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Some servers don't stop properly.
Calling `:LspStop` _twice_ will induce a force-stop, but that is not easy to
discover: https://github.com/neovim/neovim/blob/b67eff38fe19876ab228007897224ec04b58aa40/runtime/lua/vim/lsp/client.lua#L864-L866
> By default, it will just request the server to shutdown without force. If
> you request to stop a client which has previously been requested to
> shutdown, it will automatically escalate and force shutdown.
Solution:
Nvim should automatically force-stop after X seconds, but until that is
supported, adding a bang "!" variant is reasonable.
|
| |
|
|
|
|
|
| |
This option does not actually say what its purpose is, and it likely is
no longer relevant.
close #4136
|
| | |
|
| | |
|
| |
|
|
| |
fix #3941
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Problem:
:LspStop/:LspRestart support multiple args, which is unlikely to be used
for interactive usage. These commands are intended for interactive
usage, not scripts. Scripts should use the vim.lsp API.
Solution:
It is unlikely that users specify multiple args, so let's drop it to
simplify the code and interface.
|
| |
|
|
|
|
|
|
|
| |
Problem:
After the refactoring in e4d1c8b for Neovim 0.11.2 this command now
requires an argument.
Solution:
Restore the previous behaviour where `:LspRestart` defaults to
restarting all active servers.
|
| |
|
|
| |
fix #3836
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Now that vim.diagnostic.goto_prev() and vim.diagnostic.goto_next() have
been deprecated, update the README with up-to-date information.
|
| |
|
|
|
|
|
| |
Problem:
Some anchor links were defined as #vim.lsp.config which doesn't work
Solution:
Fix anchor link to #vimlspconfig
|
| |
|
|
|
| |
updating vim.lsp.config anchor link href
it seems that github will remove the dots in anchor link\
this pr update the ref href to reduce confustion.
|
| | |
|
| |
|
|
|
|
|
| |
Problem:
Contributing guide describes old style of lsp configuration.
Solution:
Change to explain new style.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Nvim 0.11 has vim.lsp.config, which mostly replaces the legacy
nvim-lspconfig "framework".
Solution:
Migrate all configs to `lsp/*` variants. The old configs in
`lua/lspconfig/` are "frozen".
The new configs include these changes:
- `commands` field became raw calls to
`vim.api.nvim_buf_create_user_command` inside `on_attach`.
- `root_dir` became:
- `root_markers` whenever the file list was simple didn't need to mach `*`
- if the logic was complicated, or needed to match something like
'\*.c', it was defined as a vim.lsp.Config `root_dir` callback.
- `on_config_change` became `before_init`. I don't actually know if this
is the correct approach, but looking around the documentation of
`nvim-lspconfig` a saw that it was defined as the function that gets
called as soon as the config have `root_dir`, and so I thought
`before_init` might be the closest alternative.
- `docs.description` became a luadoc `@brief` docstring.
- `single_file_support = false`?
Co-authored-by: Aliou Diallo <aliou@users.noreply.github.com>
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Problem:
`:checkhealth lspconfig` has no benefits vs `:checkhealth vim.lsp`.
Solution:
- on Nvim 0.11+, `:LspInfo` is an alias to `:checkhealth vim.lsp`
instead of `:checkhealth lspconfig`.
- `lua/lspconfig/health.lua` will be removed in a few months.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
## Problems:
- `:LspStop` doesn't support list of client ids or config names.
- `:LspRestart` doesn't support config names although supports list of
client ids
- Command completion uses ids and names, not allowing the user to hit
enter immediately after
finding the desired server
## Solution:
- Unify `LspStop` and `LspRestart` implementation supporting lists of
client ids and
config names
- Command completion only returns config names
- Modify docs
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem:
:LspInfo has its own "inner platlform" of highlights, mappings etc. And
it doesn't integrate with :checkhealth.
Solution:
- Move the lspinfo code to a healthcheck.
- LspInfo features such as highlights, "floating window" presentation,
etc., should be added to :checkhealth in Nvim core, if they are really
needed.
- Define a "q" mapping until Nvim stable has that in :checkhealth.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
The name `server_configurations` is extremely verbose and irritatingly
formal and dogmatic. This overlong name is a constant nuisance when
reading, writing, and coding.
It's also not even correct: these configurations are just as much
"client" configurations as they are "server" configurations.
Solution:
- Rename to a shorter name.
- Leave placeholder files for any old URLs that link to the old
location.
|
| | |
|
| |
|
|
|
|
|
|
| |
- improve overview for newcomers
- call out plan for upstreaming "framework" parts to Nvim core
- guide bug reports to neovim core
- remove most mentions of wiki
fix #3202
|
| |
|
|
|
|
| |
This section is way too verbose and encourages sloppy copy-pasting. Nvim
already ships help documentation for configuring the LSP client, so
instead of duplicating that information, point users toward upstream
docs instead.
|
| |
|
| |
See https://github.com/neovim/neovim/pull/28649.
|
| | |
|
| |
|
|
|
| |
Also remove `LspAttach` and `LspDetach` examples. There are examples
included in the Nvim docs, and we should be pointing users toward that
documentation rather than duplicating it here.
|
| |
|
|
|
|
| |
Update the README with up-to-date information about Nvim defaults.
Dramatically reduce the size and scope of the code snippets. Rename
"suggested configuration" to simply "configuration".
|
| |
|
| |
Co-authored-by: ii14 <ii14@users.noreply.github.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Co-authored-by: ii14 <ii14@users.noreply.github.com>
|
| |
|
|
|
| |
I noticed that GitHub can't parse the license SPDX ID form the
license file. So I moved the copyright notice above the license
text to the bottom of the readme.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
