persistence.nvim VS mini.nvim

persistence.nvim for using session management which is useful

i use persistence.nvim plugin, and i map the commands on my dashboard so i can open my last session

I've been using vim sessions for a while now. Sessions can have their own configuration files and that's what I use for projects. For this to be actually convenient you'll need plugin like persistence.nvim to handle the sessions themselves (or make your own workflow).

I like the idea of a "config" module. Plugins like persistence and mason.nvim have it, they allow you to set variables without calling the main module.

persistence.nvim: Small session manager. I use some of its functions to also manage project local configs. It is because of this plugin I can use language servers the way I want.

persistence.nvim * Automatically save active session to a configurable directory * API to load most recent or current session based on cwd * No direct support for a telescope picker but could probably be setup with vim.ui.select()

yeah, I was planning on shimming this functionality out to another plugin. sessions have little to do with a startup gui imo. i mention in the docs using something like https://github.com/folke/persistence.nvim

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