| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
This reverts commit 589d38d3cf2e711cf848c12ed1d6ba38899a2f38.
|
| | |
|
| |
|
| |
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
- The docs are verbose.
- The "settings" param is not really clarified anywhere.
Solution:
- Mention the "settings" param in the README.
- Tighten up the wording.
- Remove the "Use a loop to conveniently call 'setup'..." advice in the
docs. It confuses users and doesn't really save much code.
- Start to reduce the scope of nvim-lspconfig.
- For example, it is redundant for it to document general LSP things.
Thus, the help section *lspconfig-lsp* was removed.
closes #1951
|
| | |
|
| |
|
|
|
|
| |
There doesn't appear to actually be a function called `format`.
Instead, I believe what we actually want here is a call `formatting`.
Co-authored-by: Kurtis Nusbaum <kcommiter@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* Fix typo
* Update chat room to point to matrix
Co-authored-by: Michael Lingelbach <m.j.lbach@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
While not strictly required, compatibility guarantees are only provided
for the latest release on the HEAD of lspconfig. Use a commit or tag
for compatibility with previous releases.
|
| |
|
|
|
|
|
|
|
|
| |
* generating the tags at docgen and modifying the
|lspconfig-server-configurations|
tag allows `:help lspconfig-server-configurations` take you to
./doc/server_configurations.md
* adding a modeline to the markdown file ensures it sets the
correct filetype
Co-authored-by: Javier López <graulopezjavier@gmail.com>
|
| | |
|
| |
|
| |
Also suggest helping test PRs with `needs-testing` label
|
| | |
|
| | |
|
| |
|
|
|
|
| |
* remove automated generation of vimdoc + ci
* unify ADVANCED_README.md and vimdoc
* rename CONFIGS.md to server_configurations.md, move into doc folder
* move CONTRIBUTING.md to .github folder
|
| | |
|
| |
|
| |
Add link to start of README
|