Add lsp servers from plugin

[LedzZm]

I am fairly new to neovim and lua, so the answer might be obvious..

I see that the servers configured in init.lua are then validated (their installation) and then enabled.

I would IDEALLY like to be able to declare lsp configs in external files but still utilize the root init.lua server initialization. Is this somehow possible in the current kickstart setup?

[Christoph-Raab]

That'd be a real improvement. Same goes for the treesitter parsers.

All config in init.lua should be extensible by some lua/custom/config files, so updating produces as little merge conflicts as possible.

[eamonburns]

I don't think it is possible without editing init.lua. But, it wouldn't take too much effort to do something like this yourself:

-- init.lua

local servers = {
  -- the un-edited LSP server configuration
}
local ok, custom_servers = pcall(require, "custom.lsp_servers")
if ok then
  servers = vim.tbl_deep_extend("force", servers, custom_servers)
end

-- lua/custom/lsp_servers.lua
return {
  zls = {
     -- my zls configuration
  },

  lua_ls = {
    settings = {
      Lua = { -- You can even override settings from `init.lua` (see `:h vim.tbl_deep_extend()`)
        codeLens = {
          enable = true,
        },
      },
    },
  },

  -- more LSP configuration
}

[LedzZm]

Would you be against having something like that be supported in kickstart?? I am fairly new to lua, so it will take some time for me to do it but I would like to give it a go and contribute, if it is something you would like to have in kickastart.

[eamonburns]

(I'm not a maintainer, so I don't have the final say)

Something that kickstart tries to be is "single-file". I would say that having a default mechanism of configuration that looks for a somewhat arbitrary file in your configuration would kind of undermine that goal (even if that file is not present in the official kickstart repository, and it is able to function without it).

Having this in your own personal configuration is completely fine, you know exactly what it is doing, because you put it there (it is also your configuration. You can do anything you want with it. Even if it "doesn't make sense")

[henryZheng727]

All config in init.lua should be extensible by some lua/custom/config files, so updating produces as little merge conflicts as possible.

I second this; to my understanding, the point of kickstart is to encourage users to modularize their own configurations. When I started using kickstart, I was pretty hesitant to make changes to init.lua for fear of creating difficult-to-resolve merge conflicts, and ended up not really trying to customize it for a while.

Line 923 of init.lua has a single line that can be uncommented to pull in user configurations from lua/custom/plugins/. I think adding something like this, loaded near the end of init.lua with comments explaining how you'd use multiple files, is a great middle ground. For users who don't want to extend kickstart at all, it retains the single-file philosophy, but for users who do, it lets you override things you don't like, while still making it essentially trivial to deal with merge conflicts.

[LedzZm]

That was exactly my thought process... For me it feel easier and safer to un-comment one line and do all MY work on separate files and keep the contrib init.lua "pure", since I plan on getting updates.

[eamonburns]

I would say that having a default mechanism of configuration that looks for a somewhat arbitrary file in your configuration would kind of undermine that goal

I now see there is already something like this:

kickstart.nvim/init.lua

Lines 922 to 923 in 0619d89

	-- Uncomment the following line and add your plugins to `lua/custom/plugins/*.lua` to get going.
	-- { import = 'custom.plugins' },

(and it looks like @henryZheng727 has already mentioned it. how did I miss that?)

So, it would not be as strange as I initially thought.

[SetsuikiHyoryu]

You can create an after/lsp/ directory in your Neovim configuration root (at the same level as init.lua).
The after/ directory and its subdirectories are automatically loaded by Neovim's runtime.

Reference :help lsp-config-merge:

When an LSP client starts, it resolves its configuration by merging the
following sources (merge semantics defined by |vim.tbl_deep_extend()| with
"force" behavior), in order of increasing priority:

1. Configuration defined for the '*' name.
2. The merged configuration of all lsp/<config>.lua files in 'runtimepath'
   for the config named <config>.
3. The merged configuration of all after/lsp/<config>.lua files in
   'runtimepath'.
   • This behavior of the "after/" directory is a standard Vim feature
     |after-directory| which allows you to override lsp/*.lua configs
     provided by plugins (such as nvim-lspconfig).
4. Configurations defined anywhere else.

For example, here is how I integrate vue_ls with ts_ls using this structure:

https://github.com/SetsuikiHyoryu/nvim/blob/main/after/lsp/ts_ls.lua