Issue with keybindings, lazy loading and session managers about lsp-zero.nvim HOT 7 CLOSED

Only solution for now seems to be re-sourcing all the buffers after restoring a session and waiting at least 1 second before doing so. This presents it's own challenges but is a workaround for now.

.../plugins/auto-session.lua

local function resource_buffers()
	vim.schedule(function()
		vim.cmd("sleep 1")
		vim.cmd("bufdo e")
	end)
end

return {
	"rmagatti/auto-session",
	opts = {
		log_level = "error",
                ...
		post_restore_cmds = { resource_buffers },
        ...
...

from lsp-zero.nvim.

I did an update on my original post with fewer steps to replicate the same issue. After executing :LspRestart only 1 buffer keeps my custom keymaps (added with the lsp.on_attach(...) handler) and the other buffers fallback to lsp-zero default keymaps instead of preserving my custom keymaps.

from lsp-zero.nvim.

I ended up migrating to my own lsp setup and both of my problems dissapeared (session managers and :LspRestart). Thank you so much for this guide: You might not need lsp-zero and for this one: lsp-zero under the hood

Here are the commits of my migration in case anyone is interested.

I opted for doing the server setups in the lspconfig plugin instead of doing them in mason-lspconfig, maybe that was the culprit of the problem but I'm not really sure.

from lsp-zero.nvim.

I could not reproduce the issue.

And I have no clue what could be the cause. default_keymaps() is not doing anything special.

from lsp-zero.nvim.

I could not reproduce the issue.

And I have no clue what could be the cause. default_keymaps() is not doing anything special.

Thank you for your reply! I'm sorry you couldn't replicate the issue. I'm willing to debug this a little bit further. I will create a minimal git repo that you can clone y and test the issue there, would that be ok?

from lsp-zero.nvim.

Okay. I manage to reproduce the issue with another config. I think the problem is that Neovim assigns your custom keybinding only to one buffer because you have {buffer = true}.

Try to use the variable bufnr when making your custom keybinding ({buffer = bufnr}). This should work.

vim.keymap.set("n", "gr", function()
  vim.print("my custom keybinding!")
end, { buffer = bufnr })

from lsp-zero.nvim.

Okay. I manage to reproduce the issue with another config. I think the problem is that Neovim assigns your custom keybinding only to one buffer because you have {buffer = true}.

Try to use the variable bufnr when making your custom keybinding ({buffer = bufnr}). This should work.

vim.keymap.set("n", "gr", function()
  vim.print("my custom keybinding!")
end, { buffer = bufnr })

I totally missed that!! This solves the issue. Thank you so much and sorry about that 😢

from lsp-zero.nvim.