Personal Neovim configuration for Digia.

This is a personal Neovim configuration using Lua and the lazy.nvim plugin manager. The configuration emphasizes performance through lazy loading and provides a comprehensive development environment with LSP support, AI assistance, and Git integration.

• :Lazy - Open lazy.nvim UI to manage plugins
• :Lazy update - Update all plugins
• :Lazy sync - Sync plugins with lazy-lock.json

• :Mason - Open Mason UI to manage LSP servers
• :LspInfo - Show LSP client information
• :LspLog - View LSP log

• Format code: <leader>rf (in normal mode)
• Code actions: <leader>ra
• Rename symbol: <leader>rr
• Go to definition: gd
• Find references: gr

1. /init.lua → /lua/digia/init.lua - Main configuration loader
2. Plugin configurations are modularized in /lua/digia/plugin/

• Options & Keymaps: Core Neovim settings in lua/digia/options.lua and lua/digia/keymaps.lua
• Plugin Categories (see lua/digia/plugin/ for actual plugin specs):
  • ui.lua: Themes, statusline, visual enhancements
  • coding.lua: Completion, snippets, AI assistance
  • lsp.lua: Language servers, diagnostics, formatting
  • git.lua: Git integration
  • telescope.lua: Fuzzy finding and search
  • treesitter.lua: Syntax highlighting and text objects

• Leader key is space (<leader>)
• Keybinding prefixes follow consistent patterns:
  • <leader>f* - File operations
  • <leader>s* - Search operations
  • <leader>g* - Git operations
  • <leader>v* - LSP operations
• Plugins use lazy loading with specific events (VeryLazy, InsertEnter, etc.)
• Environment variables for API keys are loaded from ~/.config/nvim/.env

• Automatically removes trailing whitespace on save
• Creates parent directories when saving new files
• Uses treesitter-based folding (Neovim 0.10+)
• Avante.nvim configuration switches between Claude and Copilot based on hostname

A running log of Vim/Neovim internals worth remembering - collected here so they don't have to be re-learned from scratch.

Three directories, three different jobs in the filetype pipeline.

• ftdetect/<ft>.lua — runs early, answers "what filetype is this buffer?" Contains autocmds like BufRead/BufNewFile that set filetype for patterns Neovim doesn't already recognize.
• ftplugin/<ft>.lua — runs after filetype is set, answers "now that I know it's <ft>, configure this buffer." Buffer-local options, keymaps, and commands scoped to that filetype. Neovim sources the first ftplugin/<ft>.lua it finds on the runtimepath.
• after/ftplugin/<ft>.lua — same as ftplugin/ but sourced at the end of the runtimepath, after all earlier ones (built-ins, plugins). Use this when you need to override settings a plugin's own ftplugin applied.

Rule of thumb: ftdetect = naming the file, ftplugin = configuring the buffer, after/ftplugin = having the last word.