I myself stumbled upon this issue today. Turning off single file support does prevent multiple instances of sumneko_lua from being attached to the file after the sourcing in the auto-command; however, what if we need single_file_support?

To solve this problem, I wrote a few lines of code that sort of wrap around your require('lspconfig').sumneko_lua.setup{} logic.

Note that this assumes you are calling the setup{} function in the same file containing the auto-command. For me, that's inside the plugins.lua file:

vim.cmd([[
      augroup packer_user_config
          autocmd!
          autocmd BufWritePost plugins.lua source <afile> | PackerCompile
      augroup end
  ]])

...Your other config...

--Setting up language servers
local lspconfig = require("lspconfig")
local start_sumneko_lua = true --boolean defaults to true, otherwise, the server will never start
local current_buf_id = vim.api.nvim_get_current_buf()
local servers_attached_to_current_buf = vim.lsp.get_active_clients({bufnr = current_buf_id})

for _, server in ipairs(servers_attached_to_current_buf) do
    if server.name == "sumneko_lua" then --an instance of sumneko_lua is already attached to the buffer
        start_sumneko_lua = false 
    end
end

--After that, all you have to do is to wrap sumneko lua's setup() call inside a conditional using the boolean

if start_sumneko_lua then
    lspconfig.sumneko_lua.setup{
         -- yada yada yada
    }
end

--Other servers don't need this, so their setup can be called as usual
lspconfig.pyright.setup{

}

--yada yada yada...

The idea is simply to use some kind of "flag" to determine whether or not to call the setup() function for sumneko_lua (since the setup function determines the availability of the language server). The flag defaults to true but will be switched to false if the current buffer already has an instance of sumneko_lua attached to it.

Granted, the code is a bit inelegant and 'hackish', but it worked without any issues for me because all my plugin configuration is inside packer.nvim's plugin specification file (plugins.lua).

I hope this helps.

Multiple language server instances on save #4

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions