| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
By default, the Microsoft Python Language Server already gets an
existing Python interpreter and version from $PATH if the setting is an
empty string or null.
https://github.com/microsoft/python-language-server/blob/838ba78e00173d639bd90f54d8610ec16b4ba3a2/src/LanguageServer/Impl/Implementation/Server.cs#L143
Looking for `python` and launching the interpreter to get the
version on our end is redundant and time-consuming.
|
| |
|
|
|
| |
Remove meaningless code comments because they are increased by copy and paste.
Currently, utf8 options are only supported by clangd, so remove them from unnecessary ones.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
notification
related with #127
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
`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
|
| | |
|
| | |
|
| |
|
| |
vim.fn.has('xxx') returns 1 or 0 that both are true in lua.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Lua is easy to use from Vimscript, there is no reason to have multiple
ways to work with nvim-lsp.
- massively clarifies the "story" that users need to comprehend
- reduces surface area, maintenance, tests
- avoids constant "Vim or Lua" dance in the documentation
- simplifies discussions, tutorials, etc.
- avoids confusing situation for users that start with Vimscript but
later need Lua-only features
|
| |
|
