You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using deoplete, and I added vimproc to my list of plugins and ran make in the directory. I'm not sure what I can do to debug this and see what's actually going wrong. When I try and do the completion sequence, I get monster.vim - failed async completion in the status line. Anyone have a method to debug this and figure out what I've done wrong?
Here's what I added to my neovim init.vim
Plugin 'Shougo/vimproc.vim'
Plugin 'Shougo/deoplete.nvim'
Plugin 'osyo-manga/vim-monster'
...
" enables monster.vim async
let g:monster#completion#rcodetools#backend = "async_rct_complete"
" deoplete
let g:deoplete#enable_at_startup = 1
let g:deoplete#enable_smart_case = 1
let g:deoplete#enable_refresh_always = 1
inoremap <expr><TAB> pumvisible() ? "\<C-n>" : "\<TAB>"
let g:deoplete#sources#omni#input_patterns = {
\ "ruby" : '[^. *\t]\.\w*\|\h\w*::',
\}
I use vundle to do my package management.
The text was updated successfully, but these errors were encountered:
I get the same error, installed all dependencies as indicated, rcodetools etc. My neovim has perfect health.
I think README file must have more detailed instructions.
I have this problem on MacOS also. Last time I got it working it was on WSL (Ubuntu on Windows) and that's not more than 6 months to 1 year ago. I guess there could be an issue with either a /tmp dir on MacOS or a different problem.
I'm using deoplete, and I added vimproc to my list of plugins and ran make in the directory. I'm not sure what I can do to debug this and see what's actually going wrong. When I try and do the completion sequence, I get
monster.vim - failed async completion
in the status line. Anyone have a method to debug this and figure out what I've done wrong?Here's what I added to my neovim init.vim
I use vundle to do my package management.
The text was updated successfully, but these errors were encountered: