keymap not works anymore in version 1.12.2

[JunfengJia]

{
"before": [
""
],
"after": [
"",
"",
"s"
],
},

It will insert junk string now.
expected:
launch easymotion find char.

[gee-forr]

I'm having the same problem with triggering easymotion... my easymotion trigger is <leader><leader>w, or space, space, w.

In my case, it selects the entire line as if I was typing V in normal mode.

In the meantime, I've downgraded to 1.11.3.

[visheshd]

Had to downgrade to 1.11.3 as well

[J-Fields]

@gee-forr @visheshd what platforms are you on?

[Venefilyn]

@J-Fields same issue here, fedora 31

[gee-forr]

@gee-forr @visheshd what platforms are you on?

I'm on macOS Catalina, running the latest VS Code, and at the time, the latest VSCode Vim.

Merry Christmas :)

[visheshd]

@gee-forr @visheshd what platforms are you on?

I'm on macOS Catalina as well. Thanks for looking into it!

[J-Fields]

Thanks for the responses, all. I actually don't have access to a unix system at the moment, and it seems like this issue (as well as several other recent ones) are not reproducible on windows. If anyone could help track down what might be causing this, that would be awesome 🙂

[cvaldev]

Are any of these reproducible with vim.vimrc.enable set to false?

[Venefilyn]

Are any of these reproducible with vim.vimrc.enable set to false?

Seems to work just fine with vim.vimrc.enable set to false

[cvaldev]

@SpyTec is there by chance a line in your vimrc that remaps a plugin function. Something that looks similar to this:

nmap s <Plug>(easymotion-s2) 

[Venefilyn]

@SpyTec is there by chance a line in your vimrc that remaps a plugin function. Something that looks similar to this:

nmap s <Plug>(easymotion-s2) 

You'd be correct, I do have a mapping for easymotion in my .vimrc

[JunfengJia]

fixed In 1.12.4.