bug/feature: partial mapping (aliases) don't work as expected

[MattSturgeon]

Did you check the docs?

• I have read all the which-key.nvim docs

Is your feature request related to a problem? Please describe.

When I map "<leader>w" to "<C-w>", I don't get the which-key popup for <C-w> when typing <leader>w.

• If I type <C-w> manually, the "wondow" mappings are displayed.
• If I type <leader>w, C^W is shown in the status bar, however which-key's window does not appear.

Describe the solution you'd like

"Alias" mappings should be detected by which-key and displayed

Describe alternatives you've considered

Alternatively, "aliases" could be manually configured during plugin setup.

e.g.

operators = { --[[ ... ]] },
key_labels = { --[[ ... ]] },
key_aliases = {
  ["<C-w>"] = { "<leader>w", "gw" },
},

Additional context

Extra ideas:

• Sibling aliases could be grouped together
• All known aliases could be listed next to mappings
• Aliases could inherit the base-key's description when the alias doesn't have one

[adrianchongseek]

You can try something like this:

return {
  'folke/which-key.nvim',
  config = function()
    local wk = require('which-key')
    wk.register({
      ["<leader>"] = {
        w = {
          '<cmd>WhichKey <C-w><cr>', 'Window actions'
        },
      },
      ["gw"] = {
        '<cmd>WhichKey <C-w><cr>', 'Window actions'
      }
    })
  end
}

This is not perfect, but it will work like you expect.

[MattSturgeon]

You can try something like this: ``["w"] = { 'WhichKey ', 'Window actions' }`

This is not perfect, but it will work like you expect.

Thanks, calling :WhichKey [[action]] manually is a decent workaround, other than which-key opening instantly (without any delay) it seems to achieve what I wanted.

I'll leave this issue open so that @folke can consider the underlying issue, feature request and/or adding the workaround example to the docs (etc).