How isturiz/nvim works
Project type and purpose
• This is a personalized Neovim configuration repository (a dotfiles-like project) written in Lua.
• Its purpose is to bootstrap and manage Neovim with a set of plugins, language servers, key mappings, and editor options to streamline the developer’s workflow.
File structure
• Top-level files:
• init.lua – the Neovim entry point
• lazy-lock.json – lockfile for the lazy.nvim plugin manager
• after/ftplugin & after/plugin – filetype-specific and general Vimscript/Lua autocommands loaded “after” startup
• lsp/ – per-language LSP configuration modules
• lua/config/ – core Neovim settings (options, keymaps, plugin manager init)
• lua/plugins/ – individual plugin configuration files
• Plugin manager: lazy.nvim is initialized in lua/config/lazy_init.lua.
• LSP installation: handled by the Mason plugin (installed via lazy.nvim) and configured via modules in lsp/.
README for additional insights
• Describes requirements (Node.js for certain plugins, Mason).
• Describes plugin installation (:Lazy install) and update (:Lazy update).
• Conventions: lua/config for core setup, lua/plugins for per-plugin overrides.
Components
a. Main components
• Neovim Core – built-in runtime
• Plugin Manager – lazy.nvim
• Configuration Layer
– Core settings (options.lua)
– Keymaps (keymaps.lua)
– Plugin definitions (lazy_init.lua)
• Plugin Modules – individual Lua files under lua/plugins/
• Filetype Plugins – after/ftplugin/*.lua
• LSP Configuration – lsp/*.lua
• External Services
– LSP servers (rust_analyzer, pylsp, lua_ls, etc.)
– Node.js for plugin tooling
– Mason (manages LSP/server installations)
b. Relationships & interactions
1. Neovim Core → loads init.lua
2. init.lua → calls lazy_init → lazy.nvim
3. lazy.nvim → installs & loads plugin modules from lua/plugins/
4. Core settings & keymaps injected at startup
5. on FileType event → after/ftplugin/*.lua apply filetype-specific settings
6. Mason plugin → ensures LSP servers are present
7. Plugin ‘nvim-lspconfig’ → loads lsp/*.lua modules → spawns LSP servers
8. Plugins such as autopairs, gitsigns, copilot → attach to buffer events
c. Architectural patterns & design principles
• Modular configuration: each plugin or feature in its own Lua file
• Lazy-loading: plugins only start when needed (via lazy.nvim)
• Separation of concerns: core options/keymaps vs. plugin logic vs. filetype overrides
d. Key technologies
• Neovim (Lua API)
• lazy.nvim (plugin manager)
• Mason (LSP installer)
• nvim-lspconfig (LSP client)
• Various community plugins (telescope, gitsigns, treesitter, etc.)