nvim-snippy
pycodestyle.nvim | nvim-snippy | |
---|---|---|
3 | 11 | |
- | 288 | |
- | - | |
- | 6.7 | |
- | 7 days ago | |
Lua | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pycodestyle.nvim
-
Why aren't there more plugins written in python?
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.
-
Why Rust ?
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.
-
[plugin] pycodestyle.nvim
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.
nvim-snippy
-
luasnip-latex-snippets.nvim: A collection of smart (LaTeX) snippets for the LuaSnip plugin
nvim-snippy?
-
ISSUE: Can't expand snippets suggested by LSP
I don't know about LuaSnip, but nvim-snippy can expand LSP snippets without using an auto-completion plugin.
-
[plugin spotlight] nvim-snippy, an excellent minimalist snippet plugin
I want to give some attention to the excellent nvim-snippy plugin.
-
lsp-zero - bug with nvim-cmp duplicating parts of the string after completion
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
-
nvim: coq vs cmp
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).
-
"Suckless" Neovim plugins
there is nvim-snippy
-
Why aren't there more plugins written in python?
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.
-
Nvim + nvim-cmp + luasnip jumps to previous snippets
I switched to snippy because I had the same problem
-
Tried to use vim as a REST client. What do I miss?
Snippy for snippets,
-
Caution: Recent breaking changes to LuaSnip and cmp_luasnip.
I recommend to use https://github.com/dcampos/nvim-snippy, I'm so happy with it
What are some alternatives?
pycodestyle - Simple Python style checker in one Python file
LuaSnip - Snippet Engine for Neovim written in Lua.
xbase - Develop Apple software products within your favorite editor.
vim-medieval - Evaluate Markdown code blocks within Vim
kok.nvim - Fast as FUCK nvim completion. SQLite, concurrent scheduler, hundreds of hours of optimization.
rest.nvim - A fast Neovim http client written in Lua
coreutils - Cross-platform Rust rewrite of the GNU coreutils
vim-rest-console - A REST console for Vim.
Fennel - Lua Lisp Language
nvim-typora - Bindings for Typora's Markdown in Neovim
ultisnips - UltiSnips - The ultimate snippet solution for Vim. Send pull requests to SirVer/ultisnips!
toggleterm.nvim - A neovim lua plugin to help easily manage multiple terminal windows