The plugin that brings the “starter” / “welcome” screen when nvim
is called without a file is mini.starter
, a lua module of the mini
plugin. My primary use case for neovim is closer to a feature complete text editor rather than a full fledged IDE, although there definitely is some overlap in my setup.
My set of plugins are roughly as follows
vim-plug
, I will likely replace this one withpacker
at some pointgoyo.vim
andlimelight.vim
for distraction free viewing and editingnnn.nvim
to integrate thennn
file manager into neovimmini.nvim
according to the Github, “Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort. They all share same configuration approaches and general design principles.”mini.surround
feature rich surround actionsmini.statusline
a very simple no-frills statuslinemini.starter
aformentioned start screenmini.pairs
inserts the paired character, e.g typing(
will automatically place)
behind the cursorsmini.move
move selectionsmini.map
has a little map of the file similar to VScode among many other IDEs & text editors
barbar.nvim
Tabbar plugin- a whole bunch of LSP / autocomplete engines / snippets / git commit messages & signs
nvim-treesitter
for syntax highlighting
And the remaining things in my init.lua
file are just keybindings, setting up the plugins, and disabling the swapfile etc. when editing my password secrets in gopass
among other ‘secret’ files
The foundation supports a bunch of other open source projects, after all there is a lot more to devices that run the Linux kernel then just the kernel.
Also, I found it a but funny that the foundation created the PDF using Adobe InDesign 19.4 (Windows), according to the metadata in file posted on their website. (original | archive of the PDF)