-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sumneko_lua
asks about working environment on every startup
#1700
Comments
In the future, server usage questions should be asked on our discourse: https://neovim.discourse.group/c/language-server-protocol-lsp/7. What you're seeing is a feature of
|
For what it's worth, not everyone uses discourse, and it's appreciated that I can find the answer in the repository issues. Thanks for posting the fix! |
Would a PR be welcome, adding this to the (otherwise great) documentation? |
* refer to neovim/nvim-lspconfig#1700 * disable cmdcmp as its' annonying Signed-off-by: linxiangdong <[email protected]>
More information: neovim/nvim-lspconfig#1700 (comment)
Fix `lua-language-server` messages by disabling 3rd party checks. See neovim/nvim-lspconfig#1700 (comment).
Fix `lua-language-server` messages by disabling 3rd party checks. See neovim/nvim-lspconfig#1700 (comment).
Description
I have set up the
sumneko_lua
as shown in the docs.Every time I open Lua file this thing shows me this prompt:
I don't really understand anything about
OpenResty
andsumneko_lua
's work environments but tt seems like it doesn't save chosen settings.Neovim version
NVIM v0.7.0-dev+1004-g6bee2bf79
Build type: Release
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
2008c5c
Operating system and version
macOS 12.0.1
Affected language servers
sumneko_lua
Steps to reproduce
Install
sumneko_lua
as shown in the docs and open any Lua file.Actual behavior
As described in the description
Expected behavior
The prompt must not be shown every time I open the file
Minimal config
LSP log
https://gist.github.com/teenjuna/9c5e6cea368d0a889d204950b6161884
The text was updated successfully, but these errors were encountered: