incsearch.vim
incsearch.vim copied to clipboard
incsearch not working properly with nvim
Hi, I have a mapping in my vimrc map / <Plug>(incsearch-forward)
In Vim the mapping works correctly.
But in nvim, I am facing some strange behaviour.
When i press /, the search prompt comes with
When I paste the content from clipboard, it shows like this
Then I need to press space for the text to be visible,
But it adds 'i' before the copy pasted string.
I'm sorry for the late reply. I confirm the strange behavior in nvim.
But, I'm not familiar with neovim and I guess this must be breaking change by neovim, so I cannot fix it easily.
FYI, I'm having the same issue with one of my plugins. This is due to the absence of t_ve
in neovim which we both use to hide the original cursor.
https://github.com/neovim/neovim/commit/3baba1e7bc6698e6bc9f1d37fce88b30d6274bc9
I have created bugreport on neovim issue tracker. Seems like it will be fixed someday. If we are lucky -- until 0.2 milestone.
Thank you the info @junegunn and thank you for the report @amerlyq. cc: @zchee
I talked this bug today and revisit neovim to investigate this issue. I also noticed that t_ve
is absent. (sorry @Mariappan, if I should take a look at this issue carefully before, I must find what is the problem at least)
This is working correctly for me in nvim now @haya14busa
NVIM v0.1.6-262-g978c1fd -- Build type: Release
Thank you for the information! It seems that related issues in neovim aren't closed https://github.com/neovim/neovim/issues/3688 but anyway, i'll try it later in neovim.
oops nevermind, still see double sorry
np
It's still broken for me in 0.2.0.
There was progress in configuring the cursor in 0.2.0 but hiding it isn't doable yet. It's being actively developed, though, in neovim/neovim#6566.
The following setting will highlight the matched pattern when typing.
if has('nvim')
set inccommand=nosplit
endif
@haya14busa The corresponding neovim issue #3688 has been closed since January and the new functionality to hide the cursor (hi Cursor blend=100
) is available in the freshly released 0.5.0-dev build. See the end of the issue for the resolution summary. I'd highly appreciate if you looked into it once more to adopt the fix for your plugins.