luabundler VS mini.nvim

I wonder if a bundler would help? For example: https://github.com/Benjamin-Dobell/luabundler. I haven't tried it but in theory you should be able to point it at your home configuration and get a single file that includes it all.

So short of trying to fix the code, of which most of us are not equipped to do, what can we do? Well, there is a really fun little tool called luabundler. This tool will analyze the Lua file you feed it, figure out all the dependency Lua scripts based on the require statements, and then wrap them all up in one self-contained Lua script! All we need is Node, the bundler, and the individual scripts.

There's also a stand-alone CLI https://github.com/Benjamin-Dobell/luabundler

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