iTerm2 cursor shape will be changed by (easymotion-overwin-f2)

[shunyaoshih]

As the title, the following operation will change my cursor shape( underline ) to vertical box in iTerm2.

" s{char}{char} to move to {char}{char}
nmap s <Plug>(easymotion-overwin-f2)

While others work well on my machine, such as ...

" Move to line
map <Leader>L <Plug>(easymotion-bd-jk)
nmap <Leader>L <Plug>(easymotion-overwin-line)

" Move to word
map  <Leader>w <Plug>(easymotion-bd-w)
nmap <Leader>w <Plug>(easymotion-overwin-w)

Is there anyone having the same issue?

My environment: OS X El Capitan 10.11.6 iTerm2 version: 3.0.15

[vicheanak]

Yes, I'm having the same issue.

[shunyaoshih]

I found that this happens only when I use Neovim. Now I consider to use Vim instead...

[paulo]

Having the same problem, using NeoVim. I know this is kind of an old issue, but does anybody have a solution?

[rtucek]

TL;DR (workaround);

Put this in your .vimrc: set guicursor=

And start Neovim like so (you may want to alias this...): VTE_VERSION=100 nvim

Explanation: From Neovim's FAQ

Note: some plugins like "ctrlp" override guicursor even when it is empty. To totally disable cursor updates, you can set VTE_VERSION="100". But it would be better to fix the plugin: it should not modify guicursor if it is empty.

And yes, indeed other plugins, like CtrlP, are having the same issue with the cursor (my workaround works too with them). As far as I know this started with Neovim v2.0 upwards.

I hope @haya14busa and other plugin maintainers will fix this.

[shunyaoshih]

It seems that the authors have no longer maintained this plugin, but finally, I found an another workaround which works in the latest Neovim.

https://github.com/gantheory/vim-easymotion/commit/3051ddcd079967afeb883137a1227476b06ae339

The problem may come from here, we need to check whether guicursor is set or not. Thank @rtucek!

Though I can maintain my own cursor after this change, there is still a problem. My cursor (an underscore) will show after the block in the bottom line. Anyway, this solution is fine for me and if I have more time in the future, I will try to replace that block with the cursor controlled by the terminal If anyone want to adopt this change, just use this fork as a vim plugin

# use vim-plug
Plug 'gantheory/vim-easymotion'

[tmpm697]

same issue with neovim, set this in .vimrc help: autocmd OptionSet guicursor noautocmd set guicursor=

[unenglishable]

why does it still do this in 2022?? 😢