How do I get Rustaceanvim to use the default lsp keymaps?

[Radrahil]

For context, I'm using nvchad. Here's my lspconfig file

local configs = require("nvchad.configs.lspconfig")

local on_attach = configs.on_attach
local on_init = configs.on_init
local capabilities = configs.capabilities

local lspconfig = require("lspconfig")
-- if you just want default config for the servers then put them in a table
local servers = { "html", "cssls", "tsserver", "clangd", "pyright" }

for _, lsp in ipairs(servers) do
	lspconfig[lsp].setup({
		on_init = on_init,
		on_attach = on_attach,
		capabilities = capabilities,
	})
end

[mrcjkb]

Hey 👋

Tip

See the TIP box in the readme's Quick setup section 😄

[Radrahil]

vim.g.rustaceanvim = function()
  return {
    server = {
      on_attach = function (client,bufnr)
      end
    }
  }
end

This doesn't work. I'm supposed to put this in my lspconfig right?

I do get a warning unused local bufnr

[Radrahil]

Wait, @mrcjkb , do I have to do something else to get my keymaps to be the same as that of the other lsps?

[Radrahil]

local configs = require("nvchad.configs.lspconfig")

local on_attach = configs.on_attach
local on_init = configs.on_init
local capabilities = configs.capabilities

local lspconfig = require("lspconfig")
-- if you just want default config for the servers then put them in a table
local servers = { "html", "cssls", "tsserver", "clangd", "pyright" }

for _, lsp in ipairs(servers) do
	lspconfig[lsp].setup({
		on_init = on_init,
		on_attach = on_attach,
		capabilities = capabilities,
	})
end

vim.g.rustaceanvim = {
	tools = {
		-- ...
	},
	server = {
		on_attach = function(client, bufnr)
			-- Set keybindings, etc. here.
      vim.keymap.set("n", "K", function() vim.cmd.RustLsp { "hover", "actions" } end, { buffer = bufnr })
		end,
		default_settings = {
			-- rust-analyzer language server configuration
			["rust-analyzer"] = {},
		},
		-- ...
	},
	dap = {
		-- ...
	},
}

This does not let even the defined K keybinding work.
Even this

local configs = require("nvchad.configs.lspconfig")

local on_attach = configs.on_attach
local on_init = configs.on_init
local capabilities = configs.capabilities

local lspconfig = require("lspconfig")
-- if you just want default config for the servers then put them in a table
local servers = { "html", "cssls", "tsserver", "clangd", "pyright" }

for _, lsp in ipairs(servers) do
	lspconfig[lsp].setup({
		on_init = on_init,
		on_attach = on_attach,
		capabilities = capabilities,
	})
end

vim.g.rustaceanvim = {
	tools = {
		-- ...
	},
	server = {
		on_attach = function(client, bufnr)
			-- Set keybindings, etc. here.
			vim.keymap.set("n", "K", function()
				vim.cmd.RustLsp({ "hover", "actions" })
			end, { buffer = bufnr })
			vim.keymap.set("n", "gD", vim.lsp.buf.declaration, bufnr)
			vim.keymap.set("n", "gd", vim.lsp.buf.definition, bufnr)
			vim.keymap.set("n", "K", vim.lsp.buf.hover, bufnr)
			vim.keymap.set("n", "gi", vim.lsp.buf.implementation, bufnr)
			vim.keymap.set("n", "<C-k>", vim.lsp.buf.signature_help, bufnr)
			vim.keymap.set("n", "<space>wa", vim.lsp.buf.add_workspace_folder, bufnr)
			vim.keymap.set("n", "<space>wr", vim.lsp.buf.remove_workspace_folder, bufnr)
			vim.keymap.set("n", "<space>wl", function()
				print(vim.inspect(vim.lsp.buf.list_workspace_folders()))
			end, bufnr)
			vim.keymap.set("n", "<space>D", vim.lsp.buf.type_definition, bufnr)
			vim.keymap.set("n", "<space>rn", vim.lsp.buf.rename, bufnr)
			vim.keymap.set({ "n", "v" }, "<space>ca", vim.lsp.buf.code_action, bufnr)
			vim.keymap.set("n", "gr", vim.lsp.buf.references, bufnr)
			vim.keymap.set("n", "<space>f", function()
				vim.lsp.buf.format({ async = true })
			end, bufnr)
		end,
		default_settings = {
			-- rust-analyzer language server configuration
			["rust-analyzer"] = {},
		},
		-- ...
	},
	dap = {
		-- ...
	},
}

--
-- lspconfig.pyright.setup { blabla}

does not seem to do anything

[mrcjkb]

You should be able to be able to put it anywhere, as long as it's sourced before the plugin initialises (which is on ftplugin after you open a rust file).

If it's not working, it could be that nvchad is doing something funky, so I would suggest asking there.

I did find this discussion, maybe it will help you:
NvChad/NvChad#2594

[Radrahil]

Thank you, that worked!