Thanks for the suggestion! Glad it helped!

If you mean sponsor 'mini.nvim', then not quite yet. You can follow this GitHub issue to know when it's possible: github.com/nvim-mini/mi...

Very nice and informative. I'd add two things:
- There can be several highlight groups applied to a single cell and they can "combine" their attributes. How exactly - depends on how they are applied.
- Mention the `@variable.lua` type of groups and their nesting/fallback nature.

Today also is a birthday of 'mini.nvim' (4 years) and 'mini.pick' (2 years). So let's celebrate this together! 🎉

This is more than I could have hoped for. Thank you for your time doing this!

Left more details in the gist's comment.

Just to be clear: I am not advocating for you (or anyone) to move away from Helix. I think having a more informed decision will be a win-win situation here :)

Notes would be helpful. Thanks!

I am the 'mini.nvim' (github.com/nvim-mini/mi...) author. It contains a lot of useful modules. Better grep can come from 'mini.pick' and reference window can come from 'mini.clue'.

But it is Lua/Neovim only. So based on the other response, might not be a good fit.

Ah, that makes sense.

If you want to have a single Vimscript config for both Vim/Neovim, there is a way to source code only for Neovim: guard it behind `if has('nvim')`. Using Lua code in Vimscript is possible with `lua << EOF ... EOF` (see `:h lua-heredoc` in Neovim).

I am a part of Neovim team and author of plugins that improve mentioned behavior (there are many such plugins).

We are continuously trying to improve Neovim's "out of the box" LSP experience. So if you used those approaches, any feedback would be appreciated. If not - completely fine, of course :)

Not to detract from Helix (which is great), but for reference:
- Did you use new Neovim's `vim.lsp.enable` + `vim.lsp.config` together with 'neovim/nvim-lspconfig' plugin? The server setup is usually one line.
- Did you try dedicated plugins for better search and quick reference window?

However, usable `vim.pack` out of the box without wrappers is the design goal. It already is, just need to iron out several creases.

I've read comments that "lazy load everything" people were converted to "just list all plugins in `vim.pack.add()`". There are opposite comments, sure. That's okay.

Ah, okay. I *kind of* agree for users that want everything to work out of the box *exactly* how it used to with other managers.

At the same time, brave people who are versed in configuring Neovim are welcome to try it out. Testing it out within documented feature set is highly appreciated.

What quality of life features do you have in mind? Making it overcomplicated is a slippery slope that also leads to overcomplicating plugin ecosystem in return.

The already current set of features is enough for an average user. It might be baaic for plugin devs, but that is much smaller group.

'mini.diff' can do "almost" that with multiple sources, but otherwise you can write your own source. Should not be too verbose with your requirements.

But the name is the beast part 😭

And it was created just before AI became so widespread.

Hi! There at least the following:
- @neovim.io - official Neovim account.
- bsky.app/profile/did:... - feed that tracks Neovim+Vim and some other editors. That's how I saw your post :)

Take a look at this 'mini.diff' config: github.com/echasnovski/...

There are plans to make this setup more streamlined, but no time frame yet.