| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
`config.lspinfo` is an undocumented feature that allows extending the
info shown in `:LspInfo` (`:checkhealth lspconfig`).
This feature is unwanted because:
- it's undocumented
- it adds a maintenance burden
- it provides info that should be derived from the LSP protocol itself.
Solution:
Remove support for `config.lspinfo`.
Instead, `:LspInfo` (`:checkhealth lspconfig`) should be enhanced to
automatically gather this kind of extra info from the server response.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, lspconfig had a recommended healthcheck. This was mostly
noise as its predominant use was to check if a server was installed.
This check was not accurate as vim.fn.executable is extremely primitive
and does not consider cmd_env (forwarded to uv_spawn) or language servers
that are run via an interpreter.
Furthermore, checking if a language server is executable will no longer
be a useful signal once TCP support (which allows for connecting to
already running or remote servers).
Remove for now.
|
| | |
|
| | |
|
| |
|
|
|
| |
* chore: disable blank issue template, add Discourse link
* chore: turn issue template into form
|
| |
|
| |
The <details> element is very sensitive, code blocks will not render if there is not a newline after <summary>.
|
| | |
|
| | |
|
| |
|
| |
Reiterate that you should updated your neovim nightly release before filing issues.
|
| | |
|
| | |
|
| |
|
| |
Update bug report template
|
| | |
|
| |
|
