How to start/restart the LSP server after manual LspStop

[madsamjp]

Not really an issue, more of a question. If I stop the LSP server with LspStop, then later try to start it again with LspRestart/LspStart, nothing happens. I'm guessing this is because lze isn't being triggered.

I've tried modifying my config to start with cmd = {"LspStart"} but this doesn't work:

require("lze").register_handlers(require("lzextras").lsp)
require("lze").load({
  {
    "nvim-lspconfig",
    lsp = function(plugin)
      vim.lsp.config(plugin.name, plugin.lsp or {})
      vim.lsp.enable(plugin.name)
    end,
    before = function()
      local capabilities = require("cmp_nvim_lsp").default_capabilities()
      vim.lsp.config("*", {
        capabilities = capabilities,
        on_attach = function()
          require("config.lsp.on_attach")
        end,
      })
    end,
  },
  {
    "lua_ls",
    cmd = { "LspStart" },
    lsp = {
      filetypes = { "lua" },

-- ... rest of code

What would be the correct way to lazily restart/start the language server?

Thanks!

[BirdeeHub]

So, your spec will only run 1 time.

It puts stuff in vim.lsp.config[name], and that is what manages it afterwards.

Actually, it doesnt do that, you do that here:

    lsp = function(plugin)
      vim.lsp.config(plugin.name, plugin.lsp or {})
      vim.lsp.enable(plugin.name)
    end,

About this:

cmd = { "LspStart" },

The above shouldnt matter because once it is loaded once, the spec is gone. And this trigger also would not exist anymore.

:LspStart srvname and :LspRestart srvname should use the config from vim.lsp.config?

It seems to work for me for lua, c and go? When I do restart, LspInfo is showing that the config is the same as before I stopped it, and they seem to work again after starting