usage: Unclear how to unset lspconfig keybinding about lazyvim

[folke]

I just pushed some change to make it easier to delete/add/change lsp keymaps:

  {
    "neovim/nvim-lspconfig",
    init = function()
      local keys = require("lazyvim.plugins.lsp.keymaps").get()
      -- change a keymap
      keys[#keys + 1] = { "K", "<cmd>echo 'hello'<cr>" }
      -- disable a keymap
      keys[#keys + 1] = { "K", false }
      -- add a keymap
      keys[#keys + 1] = { "H", "<cmd>echo 'hello'<cr>" }
    end,
}

The keymap definition is the same as for the lazy.nvim keys property

[al-ce]

Don't know if this is the most efficient way but I copied the entire plugins/lsp/init.lua file in my plugins/ folder (I used plugins/lsp.lua where I put some other lsp related plugin configs) because there were some other things I wanted to change. Relevant changes below:

  {
    "neovim/nvim-lspconfig",
    -- other relevant lazy.nvim settings here, including opts table
    config = function(plugin, opts)
      -- other config stuff here

      -- setup formatting and keymaps
      require("lazyvim.util").on_attach(function(client, buffer)
        require("lazyvim.plugins.lsp.format").on_attach(client, buffer)
        -- require("lazyvim.plugins.lsp.keymaps").on_attach(client, buffer)
        require("config.lsp_keymaps").on_attach(client, buffer)
      end)

    -- Other config stuff here
    })
    end
  }

I comment out the on_attach call for keymaps I think you're referring to, while keeping the format opts. Then I add a call to config/lsp_keymaps.lua (where the optional keymaps.lua/options.lua etc files are in the runtime path) that just has a copy of plugins/lsp/keymaps.lua, and from there I can comment out/edit whatever.

Again, not sure that's the most efficient way, but I like it since I can update to any other changes I want to follow with little hassle, since lazy.nvim makes updates so easy to follow.

[folke]

I'll see for an easier way to override those mapping tomorrow!