| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
| |
high level goal is to allow users some way to set filetype for a buffer in cases where they don't want to start up an LSP server, e.g. in a fuzzy finder preview
|
| |\
| |
| | |
Allow empty section string for configuration request
|
| | |
| |
| |
| |
| |
| |
| | |
microsoft/vscode-eslint requests configuration with a section of ''.
This change returns the expected settings in that case.
https://github.com/microsoft/vscode-eslint/blob/be30e933c56ea6e8e579808d5f7c7b205c8e16cc/server/src/eslintServer.ts#L668
|
| |/
|
|
| |
resolve: https://github.com/neovim/nvim-lsp/issues/264
|
| |\
| |
| | |
util: add behavior options to tbl_deep_extend function
|
| | |
| |
| |
| |
| | |
tbl_deep_extend always override extended table properties.
This behavior is not expected. This will fix #155.
|
| |/
|
|
|
| |
fix: #161. If the buffer is not actual file like the special buffer for the plugin,
it doesn't have root_dir and we should not execute lsp.start_client for that buffer.
|
| |
|
|
|
| |
If users want to change something like log_level for all servers, changing log_level for all servers is a bit tedious.
So we can make this easier by overriding util.default_config.
|
| |
|
|
|
|
| |
notification
related with #127
|
| | |
|
| |
|
|
| |
Only check command for now
|
| |
|
|
| |
- mention :packadd
- more renames
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Sending default initOptions to ra_lsp_server the init options
emits error: "failed to deserialize config: invalid length 0,
expected struct ServerConfig with 12 elements" when receiving
an empty initializationOptions from vim.lsp.
Solution: Use an empty dict instead of empty list for
default_config.init_options
LSP spec says initOptions must be a dictionary.
fix #94
fix #107
|
|
|
`nvim_lsp/skeleton.lua` is not really a skeleton, it's a `configs`
class that provides
1. actual functionality
2. a bunch of configs
Each config is added to the `configs` object (FKA "skeleton") as
a property. Those configs are not "templates", they are "configs". So we
should clean up the wording in various places to say "config" instead of
"skeleton"/"template".
Closes #64
|