Pressing gg in normal mode results in "Press ENTER or type command to continue" when cmdheight=0

[registerGen]

[jemag]

Can confirm. Happens also for gt and gT. Also seems to cause problems where gi and gf won't work properly (in the case of gi, there won't be a press enter prompt, it just won't work properly)

Note: setting the g preset to false does not help

[registerGen]

There's a (maybe unrelated? I'm not sure) discussion in neovim's repo now. neovim/neovim#19184 neovim/neovim#19185

[Shougo]

@xiyaowong OK. I have reproduced.

It seems which-key.nvim implementation problem because of https://github.com/folke/which-key.nvim/blob/535703cd4f08623e12458b5522be1f4ec2a878e7/lua/which-key/view.lua#L123

wchich-key.nvim has dummy output. It is not needed for cmdheight=0.

[Shougo]

If I comment out the line, the problem is gone.

[xiyaowong]

@Shougo got it

[registerGen]

Got it. Thank you!

[bennypowers]

This also affect gq

[rstacruz]

As a workaround for now, the bindings for g can be disabled by setting the triggers option:

require("which-key").setup({
  triggers = { "<leader>" }
})

[bennypowers]

another workaround is to patch wk at runtime

[registerGen]

OK, I'll close it now.