nvim-possession VS mini.nvim

Yes, you can use the post_hook callback in nvim-possession, for example.

This morning while reading the documentation of an awesome looking session plugin nvim-possession, I realized that I had a hidden frustration.

nvim-possession

I recently wrote nvim-possession: it isn't as feature-complete as most other session plugins, but it does only and exactly what you need (which is its market proposition), and it looks cool ;-)!

All the new commands are described in detail in the README and help file, have a look and try it out! Link to the repository.

P. S. Do you mind if I open a PR to support yet another session manager? :p

There are already some quite good session managers out there, however for my use case they all seemed to add many features I didn't need and to require learning commands, mappings and events that I didn't use. As such, I wanted to create a minimal sessions picker that only exposes listing, creation and deletion of sessions, ideally with some visual candies and browsing to make it appealing. And nvim-possession is just that: it is aimed to the ones who aren't using sessions yet (it's still one of the least used vim features from what I hear) and only want the bare minimum without digging into bigger plugins. Moreover if you already use fzf-lua you can just install this on top (as most others use Telescope only instead).

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