VSCodeVim / Vim

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

EasyMotion not working in Operator-pending mode #7468

Open andmis opened 2 years ago

andmis commented 2 years ago

Describe the bug It doesn't seem like the EasyMotion commands work in Operator-pending mode.

To Reproduce Steps to reproduce the behavior:

In a buffer, type d<leader><leader>s<something...>.

Expected behavior I expected the EasyMotion behavior to kick in, but as far as I can tell I just get dropped out of Operator-pending mode back to Normal mode after the first time I press <leader> (which for me is \, the default).

(EasyMotion works great for me in Normal, Insert, and Visual modes.)

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):

Additional context Add any other context about the problem here.

irowebbn commented 2 years ago

I've noticed the same thing as well. This is not the behavior documented by EasyMotion- when I try the same thing outside of VS Code, it works as expected. OS: Windows 10 Extension version: 1.22.2 VS Code version: 1.64.2

HalimNaim commented 2 years ago

It's not an issue with EasyMotion I think. When you press "" it exits the mode.

samogot commented 1 year ago

I experience a similar problem. My leader key is space. When I do d<space><space>s<something...> the easymotion kicks in, but instead of deleting everything within motion it just moves a cursor, as if d was never there. The cursor indicates that operation pending mode is active up until the final stroke of the easymotion input.

This example from the original easymotion suggests that it is supposed to work: https://github.com/easymotion/vim-easymotion#support-for-dot-repeat. I tried with <space><space>f motion, but it doesn't make a difference.

I can achieve what I want via visual mode, but it is less convenient and requires one additional stroke: v<space><space>s<something...>d

vdawg-git commented 1 year ago

Any updates on this issue? I just started learning Vim and this would make using it so much easier

userrand commented 10 months ago

Any updates on this issue? I just started learning Vim and this would make using it so much easier

It works with visual mode. Another option you could maybe consider, although I do not know if it works, is maybe the neovim plugin with easymotion or another easymotion like plugin but I have not tested that yet. So far, I did not like using the neovim plugin because the vim normal mode commands gj and gk do not work well as neovim is unable to tell where lines are wrapped in vscode last I checked.

jsonMartin commented 9 months ago

I'm also having this issue, can't use operators with easymotions with VSCodeVim

I also tested with multiple VSCode NeoVIM options (the other VIM plugin for VSCode), with the supported jump libraries: Leap, Hop, etc - all of them are buggy with VSCode and don't work properly