Issue with neovim and neovim gem and ruby/rails omni completion

[ikouchiha47]

Hi, I am not being able to figure out what the problem is. But when I try to autocomplete with tabs, or , it breaks. I have already posted a question here, https://github.com/Shougo/deoplete.nvim/issues/420

The error says, An error occured while calling omnifunc rubyComplete#Complete. A ruby plugin attempted to call neovim outside main thread which isn't supported by neovim gem

(Or if you could point me in the right direction)

[alexgenco]

It looks like vim-ruby spawns a thread here: https://github.com/vim-ruby/vim-ruby/blob/53c77ead60140df436c11d86aef5e1a4ef0eba94/autoload/rubycomplete.vim#L591. I'm not sure how deoplete is involved in the problem.

There isn't a good solution at the moment... if you're looking for a workaround, I would suggest just removing this block of code in your local rubycomplete.vim.

[ikouchiha47]

ok, thanks.

[alexgenco]

I've opened a pull request in vim-ruby: https://github.com/vim-ruby/vim-ruby/pull/332

[ikouchiha47]

so, it seems no one cares about vim-ruby issue, there is no activity on the PR.. is it possible that you make a rolling fork and merge it to your master ? http://stackoverflow.com/questions/23793062/can-forks-be-synced-automatically-in-github and use that vim-ruby instead

[justinmk]

Forking vim-ruby puts a big burden on neovim-ruby and/or neovim. It should be fixed upstream, in vim-ruby.

[justinmk]

@alexgenco might be worth rebasing https://github.com/vim-ruby/vim-ruby/pull/332 to "ping" the maintainers.

[alexgenco]

Just poked

[alexgenco]

Looks like it's merged now. Want to update and give it another try?

[alexgenco]

@argentum47 any luck?

[alexgenco]

Please reopen if more issues arise.