| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
capabilities #1889
Previously, vim.lsp.protocol.make_client_capabilities() was used if no
capabilities were specified in either the user-provided config or the
default config (base or server).
Now, the base default config table has a capabilities key with the value
of make_client_capabilities(). When creating the finalized configuration
for a server, it simply uses the finalized config which is the
user-provided config deep extended by the default config (which now
contains the default capabilities).
This means that users will no longer have to create their own customized
capabilities tables seeded from
vim.lsp.protocol.make_client_capabilities(). They simply need to create
the parts that are new or different from the defaults and pass that as
the capabilities. The rest of the defaults are filled in automatically.
For this to work properly, some tbl_extend calls were changed to
tbl_deep_extend. tbl_extend will not recursively update nested tables,
so using it wipes out any server provided defaults in nested config keys
(such as capabilities) and won't properly fill in the "rest" of the
capabilities if the user provided a smaller capabilities key in their
config.
Changing to tbl_deep_extend ensures server-specific configuration values
are preserved and that the finalized config at least contains defaults
for all client-supported capabilities.
For example, clangd's config default has:
```
local default_capabilities = {
textDocument = {
completion = {
editsNearCursor = true,
},
},
offsetEncoding = { 'utf-8', 'utf-16' },
}
```
Prior to this commit, this was the full
vim.lsp.protocol.make_client_capabilities() extended with those extra
values. However, if a user provided their _own_ capabilities to the
setup() function, tbl_extend wiped these extra values out and replaced
it with the users' capabilities, which was likely only
vim.lsp.protocol.make_client_capabilities() with some _other_ tweaks.
Now, clangd can simply provide the extras, and the setup() function will
normalize the config with all of user-provided, server-specific, and
base default capabilities.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ocamllsp: add dune as supported language
ocaml-lsp-server-1.11.3 enables 'dune' rpc integration
(you need a running `dune build --watch` command which provides the RPC
server).
This allows to reformat `dune` files, and to see `dune` and other build
errors as soon as you change a file (e.g. quite useful on newly created
files which would otherwise show an LSP error until first build).
Signed-off-by: Edwin Török <edwin@etorok.net>
* ocamllsp: dune-project and dune-workspace also mark roots
Although most dune projects will also have a *.opam file,
this file might be generated by the build system.
Newer versions of dune have a dune-project file to mark the root though,
and users can create a dune-workspace file as well.
Note that `dune` files themselves do NOT mark the root: they can be
present in subdirs too.
The rules on how `dune` itself finds the root are documented here:
https://dune.readthedocs.io/en/stable/usage.html#finding-the-root
"The root of the current workspace is determined by looking up a
dune-workspace or dune-project file in the current directory and its
parent directories. Dune requires at least one of these two files to
operate."
Signed-off-by: Edwin Török <edwin@etorok.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Even though this file name was removed from the official docs
https://eslint.org/docs/user-guide/configuring/configuration-files#configuration-file-formats
Eslint still supports the older `.eslintrc` and it is used in tests
https://github.com/eslint/eslint/blob/9ecd42f36462331a0d697e74323a4d24f0cf02fc/tests/fixtures/.eslintrc
The loading is done by the legacy package `@eslint/eslintrc` that is
still used by eslint itself
```
~/Documents/repositories/eslint
$ npm instll && rg '".eslintrc"' ./node_modules/@eslint/eslintrc/lib -B 6
./node_modules/@eslint/eslintrc/lib/config-array-factory.js
66-const configFilenames = [
67- ".eslintrc.js",
68- ".eslintrc.cjs",
69- ".eslintrc.yaml",
70- ".eslintrc.yml",
71- ".eslintrc.json",
72: ".eslintrc",
```
|
| | |
|
| |
|
| |
The option docs have been moved to a new page.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Add `heex` as filetype to elixirls
|
| | | |
|
| |/
|
|
|
|
|
| |
CCLS does not use .git to identify the root of a project. In addition,
it causes issues with projects that are based on the repo tool (e.g.
AOSP), which generates .git symlinks in many places in the source tree.
In such cases, CCLS incorrectly identifies subdirectories as the root.
|
| | |
|
| | |
|
| |
|
| |
Steep is a static type checker for Ruby.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
taplo was refactored and taplo-lsp was merge into taplo-cli.
see also https://github.com/tamasfe/taplo/pull/211
|
| |\
| |
| | |
Update eslint's `autocmd` example
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
See https://github.com/lunarmodules/luacheck/releases/tag/v0.26.0
lua/lspconfig/util.lua:225:40: used variable _make_config
lua/lspconfig/configs.lua:207:63: used variable _root_dir
lua/lspconfig/configs.lua:260:19: 'not (x == y)' can be replaced by
'x ~= y' (if neither side is a table or NaN)
|
| | |
| |
| |
| |
| |
| |
| | |
Remove CMD parameters for which the language server provides defaults.
Make docs simpler.
Remove markdown code fences.
Co-authored-by: Matthias Schaub <matthias.schaub@posteo.de>
|
| | |
| |
| |
| |
| |
| | |
Example of how to use the 'cmd' setting is not needed.
Also the name of the language server in this example is wrong.
Co-authored-by: Matthias Schaub <matthias.schaub@posteo.de>
|
| | |
| |
| | |
Co-authored-by: Matthias Schaub <matthias.schaub@posteo.de>
|
| | |
| |
| | |
Make it more obvious not to copy/paste default_config
|
| | | |
|
| | |
| |
| |
| | |
This is a theorem prover (https://github.com/digama0/mm0) in some sense
related to the existing (supported) Lean theorem prover.
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
The [`@volar/server`](https://github.com/neovim/nvim-lspconfig/pull/1770) NPM package has been renamed to [`@volar/vue-language-server`](https://www.npmjs.com/package/@volar/vue-language-server).
The change to the server config was already made in https://github.com/neovim/nvim-lspconfig/pull/1770 so this is just updating the docs.
|
| |
|
|
|
|
| |
See https://github.com/johnsoncodehk/volar/issues/876
Add new languageFeatures.implementation = true option
as per CHANGELOG.md in volar repo for version 0.33
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This bug was introduced in #1324.
When calling `:LspStop <args>`, the current code tries to match a string
with the format "123 (blablabla)", which will result in terminating the
server with ID 123. This is fine when using autocompletion, but if doing
this programmatically (or just following the docs) something like
`:LspStop 1` will not match anything, resulting in terminating *all*
managed servers.
This should be enough to fix the bug, allow terminating multiple servers
at once and keeping the nice UX provided by the autocompletion.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
style(hhvm): add space inside array
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
