How do we customize the cmd for Neovim's LSP to work with LazyVim?

[nickjj]

On https://docs.rubocop.org/rubocop/usage/lsp.html it mentions we can do this to start the LSP:

vim.api.nvim_create_autocmd("FileType", {
  pattern = "ruby",
  callback = function()
    vim.lsp.start {
      name = "rubocop",
      cmd = { "bundle", "exec", "rubocop", "--lsp" },
    }
  end,
})

I noticed the cmd is something we can modify.

I run my applications in Docker so I tried:

vim.api.nvim_create_autocmd("FileType", {
  pattern = "ruby",
  callback = function()
    vim.lsp.start({
      name = "rubocop",
      cmd = {
        "docker",
        "compose",
        "exec",
        "web",
        "rubocop",
        "-c",
        ".rubocop.yml",
        "--lsp",
      },
    })
  end,
})

It might be working but I'm not 100% sure yet.

But in either case, I had to do this to disable LazyVim's rubocop configuration because it was using the default cmd.

return {
  {
    "neovim/nvim-lspconfig",
    opts = {
      servers = {
        rubocop = {
          enabled = false,
        },
      },
    },
  },
}

How would we configure things so the custom cmd is used?

This doesn't work but it demonstrates what I'd like to be able to do:

return {
  {
    "neovim/nvim-lspconfig",
    opts = {
      servers = {
        rubocop = {
          cmd = {
            "docker",
            "compose",
            "exec",
            "web",
            "rubocop",
            "-c",
            ".rubocop.yml",
            "--lsp",
          },
        },
      },
    },
  },
}

[nickjj]

Well, I don't know what changed between yesterday and today but that last code snippet is working.

You can verify it takes effect by changing something like the config path or something to be invalid. Rubocop will throw an error and log the details of that with whatever you purposely modified to be incorrect.

[nickjj]

I spoke too soon, I can't find a combination of settings that instructs the LSP to run Rubocop through a Docker command. It always falls back and tries to use what's on the host system when it comes to applying the rules.