nvim-snippy VS vim-rest-console

nvim-snippy?

I don't know about LuaSnip, but nvim-snippy can expand LSP snippets without using an auto-completion plugin.

I want to give some attention to the excellent nvim-snippy plugin.

I think it's a bug in Neovim; I ran into a similar (if not the same) issue, and I use neither nvim-cmp nor lsp-zero: https://github.com/dcampos/nvim-snippy/issues/90

I even wrote my own autocmd for auto-completion, which was a lot of fun and helped me learn a lot about Neovim. Together with nvim-snippy it meets all of my needs (so far).

there is nvim-snippy

For me it's about extra dependencies. It's not enough to just have Neovim, you also need Python and the pynvim package, plus whatever Python dependencies the plugin might have. It used to be a tradeoff worth it before we had built-in Lua, but now it doesn't really matter. The last everyday Python plugin I have is UltiSnips and I am currently evaluating nvim-snippy as a replacement.

I switched to snippy because I had the same problem

Snippy for snippets,

I recommend to use https://github.com/dcampos/nvim-snippy, I'm so happy with it

vim-rest-console[0] has been my Postman alternative for years. It basically wraps curl and makes it super easy to make different requests from a single text file. Can even write YAML and have it converted to JSON before being sent in the body. Really great tool

0: https://github.com/diepm/vim-rest-console

Been using vim-rest-console to request web services or an elasticsearch cluster.

Been using vim-rest-console for a while. You can set variables, cURL options and enable http headers to get result highlighting.

That's pretty cool. I've been using vim-rest-console for ages for this type of thing, but looking at this, maybe I should just roll my own, since that project seems to be unmaintained at this point.