parinfer-rust
pycodestyle.nvim | parinfer-rust | |
---|---|---|
3 | 15 | |
- | 516 | |
- | - | |
- | 0.0 | |
- | about 1 month ago | |
Rust | ||
- | ISC 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.
parinfer-rust
-
neovim plugins that have improved your workflow
parinfer-rust, while LISP only for reasons, is still absolutely amazing overall for its performance compared to the Lua version. I do wish there were more bracketing/scope algorithms out there for other languages. With a parinfer plugin, you only need to start a bracket for it to close what it believes is your scope. Great for enclosing things in functions
-
Why is parinfer not as good as I think it is?
While my main daily driver is also IntelliJ, and also for Parinfer, I have found that Neovim + Rust-parinfer works remarkably well.
-
Why Rust ?
Another example where rust's benefits show is something like parfiner. Currently I'm using my own ffi interface to https://github.com/eraserhd/parinfer-rust, and it feels significantly faster than the plain-lua version I had before. Getting to write the whole thing in rust just makes life easier and simpler
- paredit.vim – Paredit Mode: Structured Editing of Lisp S-Expressions
-
Lisp programming configuration for neovim
I use a combination of parinfer-rust and Conjure for my Clojure, Janet, and Fennel development.
-
Can vim become an emacs or is it already one or not?
My personal configuration is also written in fennel if you would like to take. look: https://github.com/shaunsingh/nyoom.nvim. Neovim's come a long way in what you can do with it. Fennel has a macro system as with any lisp, so you can make the syntax feel right at home with emacs https://github.com/shaunsingh/nyoom.nvim/tree/main/fnl/macros. You can even create dynamic-module like integrations with rust programs (see https://github.com/shaunsingh/nyoom.nvim/blob/main/fnl/parinfer/init.fnl, interacting with https://github.com/eraserhd/parinfer-rust/tree/master/src)
-
What are your must-have vim/nvim extensions?
eraserhd/parinfer-rust if you do any sort of Lisp programming
-
Why Clojure in a single Orgpad diagram
Clojure is an amazing language, and so is Rust. In fact, I think learning both of them is a wonderful way to introduce ourselves to such a broad range of programming ideas that it covers over half of the seven programing ur-languages. It's even worth investigating the differences in the way these languages have developed over time (Clojure being Rich's project and Rust taking a community approach). These ideas aren't in opposition to each other. If they were, the indispensable editor plugin I use to write Clojure wouldn't exist for crying out loud.
-
Parinfer fans wanted
Have you seen an excellent parinfer-rust implementation of Parinfer? It's quite fast and can be integrated with other editors, like Emacs, Kakoune, Vim, etc. I think you can try to see if your integration passes their tests.
-
Changing shift-left-right Behavior in Lisp Mode
I am currently using parinfer. It’s not exactly minimal, but it doesn’t require much configuration and doesn’t have any special keybinds.
What are some alternatives?
pycodestyle - Simple Python style checker in one Python file
nvim-ts-rainbow - Rainbow parentheses for neovim using tree-sitter. Use https://sr.ht/~p00f/nvim-ts-rainbow instead
xbase - Develop Apple software products within your favorite editor.
feline.nvim - A minimal, stylish and customizable statusline for Neovim written in Lua
nvim-snippy - Snippet plugin for Neovim written in Lua
lispy - Short and sweet LISP editing
kok.nvim - Fast as FUCK nvim completion. SQLite, concurrent scheduler, hundreds of hours of optimization.
kakoune-doas-write - Fork of kakoune-sudo-write to use doas instead.
coreutils - Cross-platform Rust rewrite of the GNU coreutils
awesome-neovim - Collections of awesome neovim plugins.
Fennel - Lua Lisp Language
nvim-dap - Debug Adapter Protocol client implementation for Neovim