nvim-snippy VS pycodestyle.nvim

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

With that said, there is still a use for remote plugins: if you really need a libraries from that ecosystem, and you would have those libraries anyway, then there is no harm done. I have a plugin called pycodestyle.nvim which makes your Pycodestyle linter configuration available in Neovim. That way I can use my linter settings as my editor settings per project, no need to keep separate settings in sync. If I want to use that plugin I need Pycodestyle installed anyway, and if Pycodestyle is not available to plugin stays dormant.

Not really. There is exactly one legitimate use case for writing plugins in something other than Lua or Vim script: if you want to use libraries written in that language. For example, I have a plugin named pycodestyle.nvim which is written in Python because it uses the Pycodestyle library to figure out the user's linter configuration. If I wanted to do it in Lua I would basically have to re-implement a major part of Pycodestyle myself, which would be a pointless waste of time. And people who use that plugin already have Pycodestyle installed anyway, so it's not an extra dependency.

Link. When I write Python I usually have pycodestyle as my linter, and this got me thinking: If I already have a linter configuration for a project, why not just use the linter configuration as my editor configuration as well? The linter configuration is useful to others even if they use a different editor and I don't have to duplicate it in a local vimrc or editorconfig file. I can just use what I already have.