Ultisnips: Neovim: KeyboardInterrupt

[rstacruz]

This frequently happens to me:

An error occured. This is either a bug in UltiSnips or a bug in a
snippet definition. If you think this is a bug, please report it to
https://github.com/SirVer/ultisnips/issues/new.

Following is the full stack trace:
Traceback (most recent call last):
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/err_to_scratch_buffer.py", line 16, in wrapper
    return func(self, *args, **kwds)
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 151, in snippets_in_current_scope
    snippets = self._snips(before, True)
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 575, in _snips
    source.ensure(filetypes, cached=autotrigger_only)
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/snippet/source/file/_base.py", line 46, in ensure
    if self._needs_update(ft):
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/snippet/source/file/_base.py", line 62, in _needs_update
    existing_files = self._get_all_snippet_files_for(ft)
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/snippet/source/file/ultisnips.py", line 183, in _get_all_snippet_files_for
    return find_all_snippet_files(ft)
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/snippet/source/file/ultisnips.py", line 35, in find_all_snippet_files
    snippet_dirs = _vim.eval('g:UltiSnipsSnippetDirectories')
  File "/Users/rsc/.vim/vendor/ultisnips/pythonx/UltiSnips/_vim.py", line 121, in eval
    rv = vim.eval(as_vimencoding(text))
  File "/usr/local/lib/python3.5/site-packages/neovim/plugin/script_host.py", line 187, in eval
    obj = self.request("vim_eval", expr)
  File "/usr/local/lib/python3.5/site-packages/neovim/api/nvim.py", line 129, in request
    res = self._session.request(name, *args, **kwargs)
  File "/usr/local/lib/python3.5/site-packages/neovim/msgpack_rpc/session.py", line 98, in request
    raise self.error_wrapper(err)
neovim.api.nvim.NvimError: b'Keyboard interrupt'

[seletskiy]

@rstacruz: I do not use neovim personally, so everything I can help you with is either consider switching to vanilla vim or investigating issue by yourself. I will gladly assist you in that case.

[joebalancio]

@rstacruz I get this too when I use ctrl-c as an alternative to esc. Try using ctrl-[ or map esc to something else

[rstacruz]

Ah yes, this seems indeed more like a problem with Neovim configuration. Here's how I fixed it on OSX.

[chrisnicola]

Updating pip does not seem to fix this problem.

Might be worth noting the YouCompleteMe recently had to address this problem.

https://github.com/Valloric/YouCompleteMe/issues/2289

[chrisnicola]

As a stopgap solution I've found adding this to err_to_scratch_buffer.py works for now. Probably not ideal, but it is unusable with the error messages popping up nearly every time I hit ctrl-C to return to normal mode.

    def wrapper(self, *args, **kwds):
        try:
            return func(self, *args, **kwds)
        except NvimError:
            return
        except Exception as e:  # pylint: disable=bare-except
            msg = \

[przem8k]

I hit this regularly (on Linux) with fresh pip packages and nvim 1.6.

[wookayin]

@rstacruz's solution does not fix the problem. I have both of g:python_host_prog and g:python3_host_prog configured in init.vim. Why don't you re-open this issue?

I am using deoplete + ultisnips under nvim 0.2.0-snapshot.

[joebalancio]

@chrisnicola @ppiet @wookayin I noticed the other day that neovim was bumped to 0.1.7. Part of that release is this PR https://github.com/neovim/neovim/pull/5546 which might address this issue although I haven't tested that theory out.

Personally, I recently started avoiding ctrl-c entirely because of this and have been very happy since.

[rstacruz]

Still happening in 0.1.7 by the way! The best solution at the moment is to avoid ctrl-c :\

[wookayin]

I think this issue needs to be re-opened.

[przem8k]

Still happening in 0.2.0. @rstacruz wdyt about re-opening the issue?