bug: whichkey menu doesn't appear in the first file that I open

[jqno]

Did you check docs and existing issues?

• I have read all the which-key.nvim docs
• I have updated the plugin to the latest version before submitting this issue
• I have searched the existing issues of which-key.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.10.0

Operating system/version

Ubuntu 24.04 LTS

Describe the bug

When I open vim and press <leader>, the which-key menu appears.
When I open any file, and press <leader>, nothing happens (after the timeout, the cursor moves one space to the left because my leader is space).
When I open another file, and press <leader>, the which-key menu appears again.

BTW, I love which-key, and version 3 looks awesome!

Steps To Reproduce

Note that I added 2 lines to the default repro file below: I set mapleader, and I define a mapping

• Run nvim with no parameters in a directory with some files
• Press leader (space): which-key menu appears
• :e somefile.txt (an existing file)
• Press leader (space): which-key menu does not appear; after the timeout, the cursor moves 1 position
• :e someotherfile.txt (an existing file)
• Press leader (space): which-key menu appears

Expected Behavior

I expect the which-key menu to appear each time, including when the first file was opened

Health

which-key: require("which-key.health").check()

- OK Most of these checks are for informational purposes only.
  WARNINGS should be treated as a warning, and don't necessarily indicate a problem with your config.
  Please |DON't| report these warnings as an issue.

Checking your config ~
- WARNING |mini.icons| is not installed
- WARNING |nvim-web-devicons| is not installed
- WARNING Keymap icon support will be limited.

Checking for issues with your mappings ~
- OK No issues reported

checking for overlapping keymaps ~
- WARNING In mode `n`, <gc> overlaps with <gcc>:
  - <gc>: Toggle comment
  - <gcc>: Toggle comment line
- OK Overlapping keymaps are only reported for informational purposes.
  This doesn't necessarily mean there is a problem with your config.

Checking for duplicate mappings ~
- OK No duplicate mappings found

### Log

```log
Debug Started for v3.3.0
on_key: <Space>
State(start): { "Mode(n)", "Node(<Space>)", { keys = "<Space>", update = true, waited = 0 } }
  continue: { "<Space>", "Mode(n)" }
  getchar
  on_key: <Esc>
  got: <Esc>
on_key: :
ModeChanged(n:c)
on_key: e
on_key: <Space>
on_key: a
on_key: .
on_key: t
on_key: x
on_key: t
on_key: <CR>
ModeChanged(c:n)
not safe
on_key: <Space>
on_key: :
ModeChanged(n:c)
on_key: e
on_key: <Space>
on_key: b
on_key: .
on_key: t
on_key: x
on_key: t
on_key: <CR>
ModeChanged(c:n)
not safe
on_key: <Space>
State(start): { "Mode(n)", "Node(<Space>)", { keys = "<Space>", update = true, waited = 0 } }
  continue: { "<Space>", "Mode(n)" }
  getchar
  on_key: :
  got: :
  reattach: { "<Space>", "n" }
  detach: <Space>
  plugin: { [2] = ":" }
  feedkeys: { "Mode(n)", "<Space>:" }
on_key: <Space>
on_key: :
ModeChanged(n:c)
attach: { "<Space>", "n" }
on_key: q
on_key: <CR>
ModeChanged(c:n)
not safe

Repro

vim.g.mapleader = ' '

vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/which-key.nvim", opts = {} },
    -- add any other plugins here
  },
})

vim.keymap.set('n', '<leader>j', function() print('hello') end)

[sjclayton]

@jqno Everything is working for me when I try to reproduce your issue following those steps, I'm also on nvim v0.10.0 and my leader key is set to space as well. Are you on the latest commit of which-key?

[jqno]

Yes: 4c36b9b
I created .config/test-whichkey and am running NVIM_APPNAME=test-whichkey nvim to test this

[jqno]

I have a pretty elaborate zsh configuration, I thought maybe that's running interference somehow, but if I blow all that away, the problem persists for me unfortunately

[sjclayton]

@jqno

I have a pretty elaborate zsh configuration, I thought maybe that's running interference somehow, but if I blow all that away, the problem persists for me unfortunately

I didn't see your minimal repro above at first, and now that I've tested again with that... I can confirm the issue occurs for me as well.

[jqno]

I can confirm that this fix works. Thanks for the super quick turnaround!