`mason-lspconfig` - Add Docs In `init.lua`

[mattcargile]

Before Reporting an Issue

• I have read the kickstart.nvim README.md.

• I have read the appropriate plugin's documentation.

• I have searched that this issue has not been reported before.

• I have ran :checkhealth and so no obvious issue.

• By checking this, I confirm that the above steps are completed. I understand leaving this unchecked will result in this report being closed immediately.

Describe the bug

powershell_es lsp didn't readily work with "empty" config like powershell_es = {},. Could we add the setup command for mason-lspconfig. It is required. Otherwise, I get the below error in lsp.log.

[ERROR][2026-07-10 20:58:57] ...ps/neovim/current/share/nvim/runtime/lua/vim/lsp/log.lua:150    "rpc"   "pwsh"  "stderr"        "\27[31;1m&: \27[31;1mThe term 'nil/PowerShellEditorServices/Start-EditorServices.ps1' is not recognized as a name of a cmdlet, function, script file, or executable program.\27[0m\r\n"
[ERROR][2026-07-10 20:58:57] ...ps/neovim/current/share/nvim/runtime/lua/vim/lsp/log.lua:150    "rpc"   "pwsh"  "stderr"        "\27[31;1m\27[31;1mCheck the spelling of the name, or if a path was included, verify that the path is correct and try again.\27[0m\r\n"

To Reproduce

1. Add powershell_es = {}, to the servers table.
2. Open file.ps1

Workaround

  require("mason-lspconfig").setup()

Desktop

• OS: Windows
• Terminal: Windows Terminal

Neovim Version

NVIM v0.12.4
Build type: Release
LuaJIT 2.1.1774638290

[mattcargile]

Ok I think I see more why this wasn't default. It is redundant with the code below to enable all in the servers variable. Maybe it would be better to have a note about how to enable specific ones. It does have some potential dependency with mason-tools-installer maybe. I ended up using the below.

  require('mason-lspconfig').setup {
    automatic_enable = false
  }

Then I used the below to make sure the tools were installed. Then I let the other plugin powershell.nvim enable the lsp, etc.

  vim.list_extend(ensure_installed, {
    'powershell_es'
  })

Not sure if mason-lspconfig is even needed anymore or if it actually is needed for mason-tools-installer to be able to negotiate the mason lsp name vs nvim-lspconfig.

I see now, one may often want to piece meal the lsp and/or dap. Or sometimes a plugin does it all.

[mattcargile]

Ok, I completely misunderstood what was going on here. Moving some of these ideas into a discussion. I see now mason-tools-installer uses mason-lspconfig's mapping methods. So setup is redundant.