Whichkey v3 now opens and interferes with my backtick bind

[unphased]

I map backtick to %'s (bracket matching) functionality via the lua bind

vim.keymap.set({ "n", "v", "o" }, "`", "%")

This I have been doing for 10+ years so I'm pretty committed to it in terms of muscle memory and I fidget around vim spamming backtick all the time these days. What this does is a recursive remap so it ordinarily takes backtick away from also being able to refer to marks. I already have the quote key to do that with anyway.

With which-key v3, it is now giving me the same menu that I get if I type ' (single quote), which is the remaining way for me to hop to a mark.

I'd like to note that my mapping still works, so hitting backtick and 1 (based on the which-key menu showing a mark to go to for the mark named '1) will simply cause %1 to be issued which is just going to hop to the match, and leave a 1 in the number accumulator, whatever that is called. What this means is that which-key appears to be assuming and mapping backtick to show the marks menu but it's already clearly been rebound to % and functions as such.

How can I fix this issue? Maybe there is a way to defer which-key startup so it learns about this particular map and gets out of my way?

Here is my lazy setup for the plugin, which is unchanged from when i introduced it a year or more ago:

  {
    "folke/which-key.nvim",
    config = function()
      vim.o.timeout = true
      vim.o.timeoutlen = 300
      require("which-key").setup({
        -- your configuration comes here
        -- or leave it empty to use the default settings
        -- refer to the configuration section below
      })
    end,
  },

[unphased]

How to disable marks plugin for which-key? That stands to be the quickest way for me outside of disabling whichkey to unblock my editor being broken at the moment.

I don't use marks (manually).

[unphased]

Found it in the readme. So this workaround is applied but i'd like to find a way to configure it better so i can still bring up the marks plugin via '.

[folke]

I actually fixed that somewhere yesterday.
Plugins (like marks) should no longer override an existing mapping.