vim-startify VS vim-obsession

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.

You must be talkng about pair programming, because that's the only situation where any of this stuff would actually matter. I haven't tried it out, but one possible solution is to just use a shared session file. You can use something like https://github.com/tpope/vim-obsession to keep it updated, and then you can decide on some heuristic to reload the session file (like on a timer, or in an autocommand).

obsssion

If you use Tim Pope's obsession, you can disable it right after closing your tab, then re-open your session. The tab you closed will still be here.

These are the main characteristics of linefly: * Small size (564 lines of Lua) * Very fast startup (almost as fast as the stock Neovim statusline) * Simple tab support (workspace tabs only, not buffer tabs) * Winbar support (works well in combination with global statusline) * Git branch detection * Git status via Gitsigns * Diagnostic status * vim-obsession and possession.nvim session support * Minimal jank as mode changes or write-status or line number changes; I don't like it when the filename moves one or two characters left or right when there are state changes. Not here. * Direct colorscheme support for these themes: moonfly, nightfly (both my own themes) along with: catppuccin, dracula, edge, embark, everforest, gruvbox,gruvbox-material, kanagawa, nightfox, sonokai and tokyonight. All other themes will use best-guess-fallback colors derived from the theme in effect.

Nice work, I may have to try this out. Currently I rely on vim-obsession and a bash function to open vim with a session file matching the name of the directory I'm in.

https://github.com/tpope/vim-obsession i like this one

Instead of a start screen, I prefer vim-obsession, Telescope, and which-key.nvim.

You might want to take a look at tpope’s obsession plugin https://github.com/tpope/vim-obsession