Hacker News Reader

Comment by lervag | Hacker News Reader

> But UltiSnips works terribly with neovim [1] [2]. Why? Because UltiSnips uses python, and neovim's python interface is 100x slower than vim's python interface. There are design decisions for this and I'm not trying to say that neovim is bad. I use both vim and neovim. But I use vim+UltiSnips+vimtex for writing LaTeX.

I'm using neovim with UltiSnips (and VimTeX), and I don't really have any big issues with it. I'm not saying you are wrongm but I do think the problem may be somewhat exagerated.

View on HN

That's interesting. My problem is very similar to the issue I labelled [2] above --- where there would be more than a second of delay in interacting with some snippets.

But somehow this suggests to me that I might have been doing something wrong. I use vim+ultisnips+(your excellent vimtex) while you use neovim. Out of curiousity, do you specifically set your python provider for your neovim in your config?

> But somehow this suggests to me that I might have been doing something wrong. I use vim+ultisnips+(your excellent vimtex) while you use neovim. Out of curiousity, do you specifically set your python provider for your neovim in your config?

Yes, I do. I use a dedicated virtual environment for neovim which I create with the following snippet; then I set the `g:python3_host_prog` accordingly [0].

    mkdir -p ~/.local/venvs/nvim
    python -m venv ~/.local/venvs/nvim
    source ~/.local/venvs/nvim/bin/activate
    pip install --upgrade pip
    pip install pynvim

[0]: https://github.com/lervag/dotnvim/blob/c3169dd18f4396258f83c...

Reply on news.ycombinator.com