vim-startify VS vim-sleuth

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.

In addition to setting tabstop and shiftwidth, you might also like this plugin: https://github.com/tpope/vim-sleuth

vim-sleuth auto detects tab size so...

Just add https://github.com/tpope/vim-sleuth and never worry about it again.

At the end of the day I don't really care which a project goes with, I've always just used vim-sleuth to automatically set my tab key to input whatever the current file's indentation is.

VsCode has an internal function from auto-detecting indentation, while my config uses vim-sleuth with indent-blankline.nvim.

If you work a lot on legacy codebases, https://github.com/tpope/vim-sleuth is probably more what you need than editorconfig, as it will work even when one is not present.

The primary advantage of using it is that it has built in heuristics for detecting line wrapping when opening a file (with some Treesitter magic for Markdown to make it more accurate), and also allows for manual swapping between wrapping types. You can think of it as the wrapping equivalent to vim-sleuth.

I just found about Tim Pope's sleuth: https://github.com/tpope/vim-sleuth It supports editorconfig but it also seems to have just better heuristics when an editorconfig file isn't present, so I just decided to replace `editorconfig-vim` with it.

Another solution is try sleuth.vim, that sets automatically your indentation based on the project, buffer and editorconfig