personal nvim cfg

Lazy-managed config built with the help of kickstart.nvim.

Prerequisites

1. Neovim v0.9.x
   • 'stable' or
   • 'nightly'
   • NOTE: I personally use v0.9.5 for now, built from source: make CMAKE_EXTRA_FLAGS="-DCMAKE_INSTALL_PREFIX=$HOME/neovim" CMAKE_BUILD_TYPE=Release && make install
2. rg
3. fd-find
4. fzf
5. unzip: sudo apt install unzip
6. git: sudo apt install git

Optional but recommended

1. xclip to enable <leader>y to yank to system clipboard: sudo apt install xclip
2. Clean up your existing nvim plugins to prevent weird clashes. Usually rm -rf ~/.local/share/nvim (backup is a good idea).
3. Get a Nerd Font for snazzy symbols. I like Fira Mono. Make sure to set it as your terminals font (not your systems).

• Don't care about a nerd font? Set vim.g.have_nerd_font = false in init.lua.

Setup

1. Clone to ~/.config/ as nvim/: cd ~/.config && git clone https://www.github.com/puttehi/nvim-lua nvim
2. Start and let Lazy do its thing: nvim

Updating plugins

Use :Lazy update. This should also update lazy-lock.json.

Structure

• init.lua: Main entrypoint, installs Lazy and imports everything.
• lua/puttehi/: Custom configuration that is imported.
• lua/puttehi/plugins: Plugins which are either in their own files (plugin per file, like nvim-colorizer.lua), or in their own category (several plugins per file, like git.lua with fugitive and gitsigns).
• lua/puttehi/vim: "Raw" configuration and Lua scripts outside of anything "plugin", such as base keymaps, :settings etc. Things that do not depend on anything but VIM installation.

Troubleshooting

General

• Start with :checkhealth. Not everything must be fixed.

Treesitter

• Start with :Lazy update + :TSUpdate.
• Find highlights under cursor with :Inspect-
• Debug node tree with :InspectTree
• Highlights refuse to work? Revert buffer to use no highlighter from TS: :TSBufToggle highlight.

LSP

• Getting some weird "could not start xxx-yyy-zzz" errors with languages? Try adding it to lsp.lua under the language server, i.e. languages["lua_ls"].tools = { "lua-language-server" }.
• Server does not seem to be working? Check :LSPInfo and if it crashed, check :LSPLog. Filetype setting (:set filetype=...) could also be wrong, check with :echo &filetype.
• :LSPRestart can work when you managed to blow up the language server, IT Crowd style.