Usage

Deployment

There’s no separate install step for this config specifically — it’s deployed as part of the Dotfiles monorepo. ~/.config is a symlink to the root of that repository, so nvim/ inside it automatically becomes ~/.config/nvim, which is where Neovim looks for its config by default.

First launch

nvim

On the very first run, lua/config/lazy.lua detects that lazy.nvim itself isn’t installed yet, clones it into Neovim’s data directory, and then installs every plugin declared under lua/plugins/*.lua. Subsequent launches just load already-installed plugins.

Prerequisites

• Neovim and git (for lazy.nvim’s bootstrap clone and plugin installs).
• A Nerd Font in your terminal — icons in Telescope, nvim-tree, lualine, and tabby all come from nvim-web-devicons and render as boxes/garbage without one.
• ripgrep for Telescope’s live_grep.
• Whichever language servers you actually want, installed and on PATH yourself: pyright-langserver, typescript-language-server, bash-language-server (see Code Explanation for how these are wired). None of them are auto-installed — the LSP setup silently no-ops for any server whose command isn’t found, so a missing server just means no LSP for that filetype, not an error.

Everyday commands

There’s no lint/test/build tooling — “correctness” for a config change means Neovim starts without errors, :Lazy shows the plugin loaded and healthy, and the specific feature behaves as expected when exercised manually.

The leader key

The leader key is never remapped from Neovim’s default, which is \. Every <leader>... keymap below is pressed as \ followed by the listed keys (e.g. <leader>ff is \ff).

Keymaps

File explorer & search

Git

LSP (buffer-local, active once a language server attaches)

AI — CodeCompanion (<leader>c*)

AI — Claude Code (<leader>a*)

Remote SSHFS

Tabs

Format on save

Every buffer is formatted via vim.lsp.buf.format() on BufWritePre, using whichever attached LSP client supports textDocument/formatting, with a 200ms timeout. There’s no separate formatter plugin — formatting quality depends entirely on the language server attached to that buffer.