vim-startify VS mini.nvim

I'm currently using alpha.nvim (https://github.com/goolord/alpha-nvim). It tries to be more generic than the others, to the point it can recreate most of the other popular ones. It even has template for for example the dashboard layout. startup-nvim (https://github.com/startup-nvim/startup.nvim) seems to do a similar thing, although I dont' have experience with that one. The only other one I've tried before is the classic vim-startify (https://github.com/mhinz/vim-startify), which is a little older I think and locks you into its layout.

Tbh, startify made me more curious about all the vim possibilities. https://github.com/mhinz/vim-startify

Just for posterity since every other session plugin has been posted, vim-startify has autosave and autoload support

I am working on a, from scratch, rebuild of the ever classic vim-startify for neovim with a focus on extreme extensibility. I also want it to be as much of a drop in replacement as possible, and don't want to write myself into a corner with some design choices I'm taking

https://github.com/mhinz/vim-startify has also means to store sessions with command 'SSave'.

might be well known but i like https://github.com/mhinz/vim-startify easy to use start screen with most recently used lists of files, etc.

Startify

mhinz/vim-startify - Start page

I was trying to center the startup screen for vim-startify and went down the rabbit hole of looking for a different startup plugin. My main use is that I want to start my already existing startify sessions as everything else I do with Telescope. I found mini.starter and it is working exactly as I want it to so I thought I would share for others that look for something similar. Don't get put off by the many components of the plugin. They are not loaded if you don't need them. Here is my a screenshot and my config for a minimal, centered, startup:

I am using :e# and ctrl-^ a lot to switch between most recent files (alternate-file), but if I open a file with startify , those commands will error with E23: No alternate file.

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