vim-startify VS vim-commentary

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.

Also, tpope/vim-commentary

https://github.com/tpope/vim-commentary does what you expect!

I've replaced most of my custom maps for commenting with tpope's commentary plugin. It's a great plugin. However, I wasn't happy with the lack of multi-line/block comment abilities so I created some maps to compliment the commentary plugin. Here are some maps that can be used with autocmd, FileType and for JavaScript comments.

commentary.vim + :h gq?

Having said this, there are some useful language independent extensions: jiangmiao/auto-pairs, tpope/vim-commentary, preservim/tagbar, junegunn/vim-peekaboo

vim-commentary comment code comfortably with motions and visual selections alike.

With a plugin like vim-commentary or comment.nvim

" This file contains common and basic plugins too essential not to include " See https://github.com/junegunn/vim-plug/wiki/tutorial " Auto install vim-plug (if not already installed) if empty(glob('~/.config/nvim/autoload/plug.vim')) silent !curl -fLo ~/.config/nvim/autoload/plug.vim --create-dirs \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim autocmd VimEnter * PlugInstall endif " Run PlugInstall if there are missing plugins autocmd VimEnter * if len(filter(values(g:plugs), '!isdirectory(v:val.dir)')) \| PlugInstall --sync | source $MYVIMRC \| endif " enable Vim-Plug: call plug#begin('~/.config/nvim/plugged') " Install/update plugins Plug 'https://github.com/tpope/vim-commentary.git' Plug 'https://github.com/morhetz/gruvbox' " Better C/C++ syntax highlighting; Plug 'https://github.com/jackguo380/vim-lsp-cxx-highlight' call plug#end() "---------- Basic configs ---------------------------------------------------- autocmd vimenter * ++nested colorscheme gruvbox " Enable transparent background let g:gruvbox_transparent_bg = 1

Commentary Tim pope's comment plugin