which-key/plugins/init.lua:10: bad argument #1 to 'pairs'

[humblehacker]

Since my searches on this issue aren't turning up anything, I'm pretty sure I must have a bug in my configuration somewhere. But before I start dissecting that, I thought I'd ask here just in case someone has seen this already.

I am running a macOS beta, so that could possibly be an issue.

Here's the error:

Error detected while processing VimEnter Autocommands for "*":
E5108: Error executing lua .../nvim/lazy/which-key.nvim/lua/which-key/plugins/init.lua:10: bad argument #1 to 'pairs' (table expected, got nil)
stack traceback:
        [C]: in function 'pairs'
        .../nvim/lazy/which-key.nvim/lua/which-key/plugins/init.lua:10: in function 'setup'
        .../pack/packer/start/which-key.nvim/lua/which-key/init.lua:85: in function 'load'
        [string ":lua"]:1: in main chunk
Press ENTER or type command to continue

which-key plugin config:

return {
  "folke/which-key.nvim",
  event = "VeryLazy",
  init = function()
    vim.o.timeout = true
    vim.o.timeoutlen = 1000
  end,
}

which-key version (from lazy-lock.json):

  "which-key.nvim": { "branch": "main", "commit": "903e468e12329ce2dc927af227b36e536eb35475" },

neovim version (installed via homebrew):

NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713773202

system info (system_profiler SPSoftwareDataType SPHardwareDataType):

Software:

    System Software Overview:

      System Version: macOS 15.0 (24A5289h)
      Kernel Version: Darwin 24.0.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: <redacted>
      User Name: <redacted>
      Secure Virtual Memory: Enabled
      System Integrity Protection: Enabled
      Time since boot: 1 hour, 19 minutes

Hardware:

    Hardware Overview:

      Model Name: MacBook Pro
      Model Identifier: MacBookPro18,2
      Model Number: MK233LL/A
      Chip: Apple M1 Max
      Total Number of Cores: 10 (8 performance and 2 efficiency)
      Memory: 64 GB
      System Firmware Version: 11881.0.224.0.2
      OS Loader Version: 11881.0.224.0.2
      Serial Number (system): <redacted>
      Hardware UUID: <redacted>
      Provisioning UDID: <redacted>
      Activation Lock Status: Enabled

[folke]

I really don't see how that can happen.
What do you do after that lazy spec?

[humblehacker]

I disabled all 25 of my plugins, and the problem was gone. And just by chance the first plugin I re-enabled caused the problem to return.

That plugin? Catppuccin

It has "integrations" for various plugins, including which-key. I disabled it by adding the following to my catppuccin config. This didn't actually do anything, I had the whole plugin disabled.

  integrations = {
    which_key = false,
  },

I'm not sure how it's applied, but this is its which-key integration:

local M = {}

function M.get()
	return {
		WhichKey = { link = "NormalFloat" },
		WhichKeyBorder = { link = "FloatBorder" },

		WhichKeyGroup = { fg = C.blue },
		WhichKeySeparator = { fg = C.overlay0 },
		WhichKeyDesc = { fg = C.pink },
		WhichKeyValue = { fg = C.overlay0 },
	}
end

return M

[folke]

that doesn't do anything which-key specific, so that can't be it

[humblehacker]

You're right. Only disabling the whole catppuccin plugin makes the problem go away. So it's something else in that plugin. I'll post something over there and update this if I learn more.

[folke]

I'm telling you it's not catppuccin. They don't load which-key in any way

[humblehacker]

Thanks for taking the time. You're right again. It is true that with no other plugins but which-key and catppuccin enabled, I get the error. And with catppuccin disabled, the error goes away. But it's not the only plugin for which this is true.

So it's something else in my setup. I'll keep looking.

[humblehacker]

Before I added which-key, I had a keymaps.lua with most of my custom keymaps that gets loaded before lazyvim.

require("core.keymaps")
require("core.options")
require("core.lazy")

As you suggested, I was calling register() somewhere. At some point after I added which-key, I added some which-key mappings to keymaps.lua -- mainly to add names to leader key groups. I suspect those mapping cause problems because which-key isn't yet loaded. Since keymaps.lua is loaded before lazyvim is set up, in retrospect I'm not sure how it was working before, but it was. I removed all references to which-key from my keymaps file, and the problem is now gone.