Unable to use it with VSCodeVim easy motion about vscode-which-key HOT 11 CLOSED

Just in case someone is having issue with easymotion.

Remove "vim.leader": " " from settings.json

from vscode-which-key.

@MarcoIeni the template is nice when you want to report a bug, but this is just a functionality that is not taken in account. I think the title and the description are descriptive enough. I'm having the same problem by the way.

from vscode-which-key.

This plugin is not using the leader key. What's your setup? Are you using VSpaceCode? Were you at one point using the leader key approach with VSpaceCode? See VSpaceCode/VSpaceCode#90

from vscode-which-key.

When you report a bug you should follow the instructions of the bug report template

from vscode-which-key.

Some of the info asked by stevenguh are part of the template, that's why I pointed it out.

from vscode-which-key.

The current <spc> j contains easy motion key bindings like <spc> j w to jump word for example. I need more description than what I have here to understand. Is there something new about easy motion that I don't know? Or is it some misconfiguration? like @MarcoIeni said, understanding what config you are running can help.

from vscode-which-key.

I'm pretty sure the problem is a combination of keybindings overrides and lack of docs (both, on this repo and on VSCodeVim one).
Not sure if this plugin uses space as default to activate the which key, but VSpaceCode does.
Given that there is no documentation about how to remap keys when you run a WhichKey command/option (I know there is now an issue for that) and that the only way according to VSCodeVim docs (https://github.com/VSCodeVim/Vim#vim-easymotion) to activate easymotion is by remapping keys (there is nothing like vim.easymotionForward) I'm pretty sure that is the root cause of this problem.

from vscode-which-key.

Not sure if this plugin uses space as default to activate the which key, but VSpaceCode does.

This VSpaceCode uses the space key to activate the which key if you choose the "automatic" installation. And both plug-ins allow you to customize which key you what to use to activate.

I know there is now an issue for that

I just link it here, so people can follow
VSpaceCode/vspacecode.github.io#3

that the only way according to VSCodeVim docs (https://github.com/VSCodeVim/Vim#vim-easymotion) to activate easymotion is by remapping keys (there is nothing like vim.easymotionForward) I'm pretty sure that is the root cause of this problem.

As far as I know, there isn't really a way to call it directly, so we have to call it with the leader key. If a user changed its leader, the easy motion might not work right off the box. We should update the doc with that information. Feel free to help us update the doc.

In the Vim repo, the current maintainer also talked about an external API for other extension to use so we might able to call directly to Vim to activate easy motion. VSCodeVim/Vim#5073

from vscode-which-key.

Documented how to use vim remap. @gquittet @danielo515 Is this still an issue?

from vscode-which-key.

Not anymore for me.

from vscode-which-key.

Docs looks awesome. Yes, I think this is not a problem anymore

from vscode-which-key.