vim-startify VS vim-rooter

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 or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.

maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim

The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:

It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.

An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter

I just use rooter and avoid thinking about it...

There's vim-rooter, which is great.

No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.