ultisnips VS coc.nvim

I always like people's LaTeX-based note taking setups. I'm a mathematician, so I write a lot of LaTeX too. (And I use vim, so I really like vim+Latex workflows).

It's interesting that this post (or rather, the later post that discusses this) talks about the advantages of UltiSnips. The well-known vim-LaTeX posts written by Gilles Castel (RIP) relied pivotally on UltiSnips.

It's not just that UltiSnips is a snippet engine. There are many of those (including LuaSnip, the other snippet engine mentioned in the OP series of articles). It's that UltiSnips can dispatch arbitrary expressions to short python code sections, and python has a great scientific library. For example, it's trivial to write a `sympy` snippet that will simplify or compute a given expression and write the output in latex for you.

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.

LuaSnip has interpolation too. I suppose it would be possible to write more code that calls from LuaSnip to a system like sympy (or other). But that's work. On the other hand, I think it takes a true power user to actually want or use the fancy interpolation functions.

[1]: https://github.com/SirVer/ultisnips/issues/974

I think in-the-wild examples like Ultisnips deoplete semshi (although they are advanced and somewhat complex) would also be good examples to learn how one can use python for writing plugins.

I didn't know lsp-zero, but this integration seems just for me except for that I am using UltiSnips instead of luasnip. Just curious how difficult do you think it is to add UltiSnips integration along with cmp-nvim-ultisnips?

If you use UltiSnips, you can just do this:

Snipets or code completion can be done in a number of different ways, and how that is configured will depend on what method you use. In the blog he uses the vim plugin ultisnips. You'll find details on configuration for that in that link.

Heyo, I've been trying to get UltiSnips and YouCompleteMe to work, however, I've ran into a bit of a problem. The python36.dll library does not seem to exist for UltiSnips, and YouCompleteMe cannot locate python at all (screenshots at bottom).

As well as its own plugins Vim/NeoVim can use VSCode's LSPs, DAPs and extensions either directly or via plugins like CoC[1] and Mason[2].

I would be surprised if emacs couldn't do the same.

1. https://github.com/neoclide/coc.nvim

The most famous TypeScript one probably is coc.nvim

It is flatly the wrong mindset to think of vim as an IDE. vim is a code editor: get in, make change, get out. Consider vim koans, which are a fun little read. You can throw coc.nvim at Neovim, along with a few other bits to give you a Good Enough setup, but vim isn't and will never be an IDE.

I just did a fresh reinstall of CoC, on a newer version of Neovim. I'm now seeing something I hadn't seen before, which CoC calls "inlay hints". They look like this:

I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

coc.nvim

There are some plugins which have the best documentations I have ever seen, but you need to read it from the Vim.

Example of coc.nvim: https://github.com/neoclide/coc.nvim/blob/master/doc/coc.txt

Actually you can with coc.nvim & coc-sh. So long as shellcheck is also installed and in PATH, it'll integrate with coc/vim just fine.

When you install an extension it runs an npm install or yarn, iirc, which is going to be problematic for you being offline. I was going to say you could copy that ~/.config/coc folder directly to the other machine but yeah, Windows, no idea. You see here https://github.com/neoclide/coc.nvim/wiki/Using-coc-extensions

You can try https://github.com/neoclide/coc.nvim, the pre-requisite is to install nodeJS, then to install all the languages LSP. This works for me for Angular, Rust, JavaScript, Vimscript, etc