parinfer-rust VS feline.nvim

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

While my main daily driver is also IntelliJ, and also for Parinfer, I have found that Neovim + Rust-parinfer works remarkably well.

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

I use a combination of parinfer-rust and Conjure for my Clojure, Janet, and Fennel development.

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)

eraserhd/parinfer-rust if you do any sort of Lisp programming

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.

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.

I am currently using parinfer. It’s not exactly minimal, but it doesn’t require much configuration and doesn’t have any special keybinds.

https://github.com/feline-nvim/feline.nvim is archived since 17 Feb 2023

I'm using feline.nvim but this question isn't specific to feline.

I use feline to generate my statusline and my winbar. This is imho the best statusline plugin for neovim in terms of configuration, truncation, default providers etc.

The "look" you're looking for is given by a bunch of plugins: - OneDark.nvim as colorscheme - TS Rainbow for rainbow brackets - BarBar for bufferline - Nvim Devicons and NerdFonts to view file icons - NvimTree as a file manager - Indent Blankline to show indentation guides - CompetiTest with vertical split UI - Feline as statusline plugin. In the screenshot feline is configured with a custom theme. As you can see statusline is different for CompetiTest buffers: a different statusline can be configured for every different filetype using conditional_config.

We have now migrated from feline to heirline

Pretty sure it isn't. Siduck used to use feline.nvim then later moved onto creating their own statusline that is specific to NvChad. You can find it here.

Hi! I'm a big fan of the feline plugin to describe a statusline. It provides a very powerful api to create your own components, which can be used in the statusline. But also, I like a way of the lualine, in which we can separate the schema of the statusline and used components. So, I've tried to combine these advantages in one place and wrote an extension for feline: dokwork/feline-theme.

Author of Feline.nvim and also the winbar PR here. I want to inform everyone who uses Feline that it now has support for winbar.

Packer failed to update feline.nvim, and I saw that it's been moved to https://github.com/feline-nvim/feline.nvim.

Hello, author of Feline.nvim here. I'll get straight to the point. A while ago I started using Semantic Versioning for Feline.nvim as it seemed like a good idea at that time. However, as time went by, it just became more and more of a hassle to release new versions, especially after development of Feline.nvim slowed down and it just needed minor bugfixes. I feel like now it's more hassle than it's worth. So I'm switching back to using a rolling-release model. From now on, the master branch will contain the latest changes. The development branch is deprecated and all development branch users need to switch to the master branch.