nvim-highlite VS mini.nvim

nivm-highlite boasts ease of configuration, but I haven't tried it yet. It shows only dark themes, but most of the themes support `background=light`. However they are kinda low contrast out of the box.

My plugin and mini.colors can also do it.

tl;dr: export your favorite themes to new formats (e.g. wezterm theme), generate new colorschemes from only a palette of colors, update old colorschemes to automatically include support for new plugins (it sometimes makes them faster too). Repo link

Wow. I just spent like an hour the other day converting colortrans to Lua because I wanted my colorscheme generator to work with all systems, but with this I can just remove built-in support for cterm and suggest mini.color for that purpose.

Mine, nvim-highlite

I do wish there was a builtin way to partially link highlight groups. In my colorscheme I opted for this syntax, which resolves self into the batch of groups being defined recursively unwraps highlight links to fetch the true highlight group being referenced.

Shameless self-plug, but nvim-highlite and all of its inheritors support everything from 8-bit to 256-bt and is written using the Neovim API.

Haven't tried newer color schemes on the block, but I have tried a lot and all of them add 100s of ms to startup time. Eventually settled on a copy of https://github.com/Iron-E/nvim-highlite. Another culprit tends to be all the fancy statusline.

Not to self advertise (regulars here know I do that enough), but my colorscheme is made to work in any range of color. If you don't like it, look under the usage section— all of the colorschemes others have made with it also work without termguicolors.

I'm a little puzzled as to why they'd do that. It's completely possible to use the :colorscheme command.

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone