triggerKey Not Firing from edamagit about vscode-which-key HOT 7 OPEN

and must contain whichKeyVisible which limits this shortcut to be only applicable when the which-key menu is visible

I think I missed that caveat. That said is there a way to trigger a submenu without which-key already visible?

from vscode-which-key.

Found one solution:

{
  "key": "shift+2",
  "command": "extension.multiCommand.execute",
  "args": {
    "sequence": [
      "vspacecode.space",
      { "command": "whichkey.triggerKey", "args": "@" },
    ],
  },
  "when": "!whichKeyVisible && editorLangId == 'magit' && vim.mode =~ /^(?!SearchInProgressMode|CommandlineInProgress).*$/"
},

It works! But downside is requires the multiCommand extension. If there's a cleaner way, I'd love to see a better solution

from vscode-which-key.

Let me make sure I understand the problem. You are trying to have @ to open the which-key menu that's equal to SPC w when the current editor is magit editor.

Your workaround is probably the best bet currently. I thought about adding keys sequence to the show API which is used by vspacecode.space so I user can bind a command to do exactly what you are trying to do.

from vscode-which-key.

Also, per buffer remapping in vim was mentioned on VSCodeVim/Vim#4765 (comment)

from vscode-which-key.

Let me make sure I understand the problem. You are trying to have @ to open the which-key menu that's equal to SPC w when the current editor is magit editor.

That’s correct.

Your workaround is probably the best bet currently. I thought about adding keys sequence to the show API which is used by vspacecode.space so I user can bind a command to do exactly what you are trying to do.

I’m willing to give a PR for that a shot if you’re open to it.

Will try the per-buffer remapping approach as well

from vscode-which-key.

I’m willing to give a PR for that a shot if you’re open to it.

Sure :) Let me know if you have any questions.

Will try the per-buffer remapping approach as well

Unfortunately, that's just a thread mentioning that functionality doesn't exist today.

from vscode-which-key.

I’m willing to give a PR for that a shot if you’re open to it.

Sure :) Let me know if you have any questions.

Great will do!

Will try the per-buffer remapping approach as well

Unfortunately, that's just a thread mentioning that functionality doesn't exist today.

Oh my mistake, I misunderstood there but your reply probably just saved me a good chunk of time 😅

from vscode-which-key.