minimap.vim VS mini.nvim

I have been trying to install https://github.com/wfxr/minimap.vim for several hours now. It installed the plugin but it won't load.

And if you really freaking wanted to, you could just add it to vim...

Prior to writing this, I didn't use any "buffer overview" plugins. I accidentally happened to see a wfxr/minimap.vim plugin, which uses Rust dependency to render text overview. This made me really curious if I could implement similar functionality in Lua with at least comparable speed. Turned out, I could! Benchmarking 'mini.map' and 'wfxr/minimap.vim' for first map window opening on 'builtin.txt' help page (9338 lines) shows around 70-90 milliseconds of computation time. Both are much faster on smaller files, of course.

https://github.com/wfxr/minimap.vim (on the right, but a minimap instead a bar)

wfxr/minimap.vim - VSCode style mini maps

I don't usually use any minimap, but when I show my configuration, there is one for decoration.

very nice. Would love to have the same feature in https://github.com/wfxr/minimap.vim

Regarding minimap in terminal, I've been enjoying this plugin.

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