• Plugins
• Directory Tree
• Files and Settings
• Installation
• LSP Configuration
• Appearance
• Keymaps
• Configuration Check
• Screenshots
• Guides and Resources
• Other Neovim Lua Projects and Examples
• Lua Resources

lazy.nvim - A modern plugin manager for Neovim

feline.nvim (freddiehaddad Fork) - A minimal, stylish and customizable statusline for Neovim written in Lua

nvim-lspconfig - A collection of common configurations for Neovim's built-in language server client

nvim-cmp - Auto completion plugin

LuaSnip - Snippet Engine for Neovim written in Lua

nvim-tree.lua - A File Explorer written In Lua

indentBlankline - Adds indentation guides to all lines (including empty lines)

nvim-autopairs - A super powerful autopairs for Neovim

Tagbar - A class outline viewer for Vim

gitsigns - Super fast git decorations implemented purely in lua/teal

nvim-treesitter - Nvim Treesitter configurations and abstraction layer

alpha-nvim - A fast and highly customizable greeter for neovim.

nvim-web-devicons - A Lua fork of vim-devicons

${HOME}/.config/nvim

/nvim

• init.lua: Main configuration file that call lua modules

• lua: The directory of lua modules, these modules are called in the init.lua file (see below).

See: nanotee/nvim-lua-guide: Where to put Lua files

/nvim/lua/core

• autocmds.lua: Define autocommands with Lua APIs

• colors.lua: Define Neovim and plugins color scheme

• keymaps.lua: Keymaps configuration file, Neovim and plugins keymaps

• lazy.lua: Plugin manager configuration file

• options.lua: General Neovim settings

• statusline.lua: Statusline configuration file

/nvim/lua/lsp

• lspconfig.lua: LSP configuration (language servers, keybinding)

/nvim/lua/plugins

• alpha-nvim.lua: Dashboard

• indent-blankline.lua: Indent line

• nvim-cmp.lua: Autocompletion settings

• nvim-tree.lua: File manager settings

• nvim-treesitter: Treesitter interface configuration

1. Install Neovim v0.10.x.

2. Install Nerd Fonts, (the font of the screenshots are JetBrainsMono Nerd Font).

3. Install Node.js - npm for download packages of LSP language servers, see: LSP Configuration.

4. Make a backup of your current nvim folder if necessary:

mv ~/.config/nvim ~/.config/nvim.backup

5. Download neovim-lua with git and copy the nvim folder in the ${HOME}/.config directory:

git clone https://github.com/brainfucksec/neovim-lua.git
cd neovim-lua/
cp -Rv nvim ~/.config/

6. Install lazy.nvim for install and manage the plugins, see: lazy.nvim - Installation

7. Run Neovim for download/sync plugins with lazy

nvim

1. Install LSP language servers with npm, see: Languages Currently Supported

sudo npm install -g \
    bash-language-server \
    pyright \
    vscode-langservers-extracted \
    typescript typescript-language-server

2. Install additional packages for plugins support:

C, C :

• clang for use LSP with clangd.

• ctags to view tags with Tagbar.

Python:

• pynvim

3. Open a source file of one of the supported languages with Neovim, and run command :LspInfo for verify the LSP support.

See: nvim-lspconfig - Quickstart

Lua - builtin

Bash - bashls

Python - pyright

C, C - clangd

HTML, CSS, JSON - vscode-langservers-extracted

JavaScript, TypeScript - ts_ls

See: nvim-lspconfig #doc/LSP configs

• OneDark

• Kanagawa

• Neovim Monokai

• Rose Pine

Fonts: See: Installation

Icons: nvim-web-devicons

See: Screenshots

The color scheme (default: OneDark) is defined in the following file:

• Neovim UI - nvim/lua/core/colors.lua:

--[[
Set Neovim UI color scheme.
Insert preferred color scheme in the `color_scheme` variable.
Color scheme is loaded at "Load color scheme" after settings sections, setup
must be called before loading.
--]]
local status_ok, color_scheme = pcall(require, 'onedark')

-- Load color scheme:
require('onedark').load()

-- Set status line color scheme
return M.onedark_dark

These are the default keymaps, in the following shortcuts, the <leader> key is set up to , (comma) character, see: keymaps.lua.

• Open nvim and run command checkhealth, you should not see any error in the output (except for the one related to the Python 2 interpreter if don't have it):

:checkhealth

• You can also use the startuptime option to read the nvim startup logs:

nvim --startuptime > /tmp/nvim-start.log

nvim /tmp/nvim-start.log

See: :help startuptime

Also you can check the plugins configuration and startup time with lazy:

:checkhealth lazy

:Lazy profile

See: lazy.nvim - Usage

• Lua - Neovim docs

• Lua-guide - Neovim docs

• Everything you need to know to configure neovim using lua

• reddit /r/neovim

• Lemmy: programming.dev/c/neovim

• NvChad

• nvim-ide

• nv-ide

• Neovim from scratch

• Learn X in Y minutes: Where X=Lua

• Lua Quick Guide

• Lua 5.4 Reference Manual

This setup is based on KISS principle, probably some concepts may not be valid for everyone. Then feel free to take what you need but don't install anything without checking first!

This setup is not a Framework but it is the configuration I use to work on Linux, it can be used by default as it can be a start point to understand how Neovim is structured and maybe improve this config. Is the base configuration I use, and it tries to stay as simple as possible, with each addition weighted along these lines.

Less is more

• All the contributors who helped improve this setup with their reports and advices.

• All the authors of the sources mentioned above.

• The users of /r/Neovim subreddit for the support of the configuration.