VSCodeVim / Vim

:star: Vim for Visual Studio Code
http://aka.ms/vscodevim
MIT License
13.9k stars 1.32k forks source link

EasyMotion Plugin does not work when vimrc is enabled #7570

Open AtivJoshi opened 2 years ago

AtivJoshi commented 2 years ago

Describe the bug EasyMotion Plugin does not work when vimrc is enabled

To Reproduce Steps to reproduce the behavior:

  1. Go to 'settings'
  2. Click on 'Vim > Vimrc: Enable' to enable it
  3. Click on 'Vim: EasyMotion' to enable it
  4. EasyMotion does not work
  5. Disable Vimrc
  6. EasyMotion starts working

Expected behavior EasyMotion should work even when vimrc is being read

Screenshots If applicable, add screenshots to help explain your problem. If remapping-related, please attach log output: https://github.com/VSCodeVim/Vim#debugging-remappings.

Environment (please complete the following information):

AlexString commented 2 years ago

Just installed Easymotion, I like the idea behind this nice plugin and I would like to use it along with Vim plugin, the thing is that when entering 'moving mode' with the defined keyboard shortcut vscode-easymotion-jumToWord alt + } it does the expected thing about showing all movable places with a highlighted keyword, neither in normal or insert mode I can't manage to move to a desired word.

It would be nice to map this vscode-easymotion-jumToWord command to vim like this

{
// Move with easymotion
"before": ["<leader>", "m"],
"commands": ["vscode-easymotion.jumpToWord"]
}

Note: I notice that when mapping this command Vim plugin does not read the 'm' and it keeps waiting on 'leader' (in the bottom prompt where it shows the pressed keys and to it's left the executed command) so I'm guessing it's not possible for vim to read the next pressed keys as somehow easymotion 'steals' the focus (?