New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
neovim: E724: unable to correctly dump variable with self-referencing container" #125
Comments
Hello! Thanks for developing this plugin. Until recently, I have used it on a regular basis and truly enjoyed its features. I am writing to report that recently I have had exactly the same issue when using Neovim and incsearch.vim. That is, the plugin crashes as soon as I run a search in Neovim. However, I can confirm that the same fault does not occur when I use this plugin in version 8 of Vim. I can confirm that this issue manifests when I load any type of file into Neovim and then perform a search with this plugin. However, searching with another plugin, such as EasyMotion, does work correctly on both Vim and Neovim. Here are some details about my current configuration:
Okay, I hope that this helps to diagnose the problem. Please let me know if there is anything that I can assist with when it comes to resolving this issue. Thanks for your hard work on this plugin! |
dup: #123 It's neovim's bug. Please report the problem to neovim. |
Considering the fact that neovim seems to port partial feature recently neovim/neovim#5529, it might be related with this issue #111 by chance. |
I reported the problem neovim/neovim#5529 (comment) cc @alok |
ref: neovim/neovim#5769 I'm guessing that this bug is introduced by the regression of porting partial feature. |
neovim/neovim#5769 is closed now but neovim/neovim#5902 mentions incsearch.vim could use |
Has anyone found a solution for this? For me incsearch still doesn't work on the latest unstable neovim. Even if it is a problem with neovim, a workaround would be great until this is resolved. |
hmmmmmmm.............. I think I know a workaround fix, but I don't use neovim and I strongly hope neovim should be as compatible as possible with Vim. maybe, you can ping neovim/neovim#5902 it seems it's not difficult to fix the problem from a quick read of this comment neovim/neovim#5529 (comment) |
@haya14busa If you do have any suggestions on a quick fix (even something temporary that we could dump in our vim config for the time being) that would be appreciated since I'm a complete novice when it comes to vimscript. |
I think you can test neovim/neovim#6070. |
@Shougo I just test the master branch, I still neovim do not segment fault, but I get some errors
|
@wsdjeg Please read this. |
Looks like this is back for me :( |
OS: macOS Sierra 10.12.2
neovim:# nvim --version
NVIM v0.2.0-164-gc1d1493e
(installed by brew install --HEAD neovim)
term: iTerm2 Build 3.0.13
After incsearch plugin loaded, when input char after slash(/) , neovim crashed with:
/ Segmentation fault: 11
The text was updated successfully, but these errors were encountered: