growing-nvim-config

Incremental migration lets you add keybindings, settings, or plugins one piece at a time. Create Lua files in assets/nvim/lua/user/, add require statements to home.nix under extraLuaConfig, then apply changes with home-manager switch. This keeps modifications scoped and reproducible across machines.

Yes. This approach automates safe, incremental growth by isolating changes in assets/nvim/lua/user and integrating them via home.nix. Each update is applied reproducibly through home-manager, reducing churn when adding features progressively.

Place Lua files in assets/nvim/lua/user/ organized by function—like options.lua, keymaps.lua, plugins.lua. Reference them in home.nix using the extraLuaConfig pattern with require statements. This structure keeps config modular and manageable during migration.

No. You can migrate settings incrementally without a full rewrite. Move individual configurations into assets/nvim/lua/user/, integrate them step-by-step via home.nix, and apply changes with home-manager switch for consistent, reproducible results.

extraLuaConfig in home.nix allows you to load Lua modules from assets/nvim/lua/user/ using require statements. This pattern keeps configuration declarative, version-controlled, and synchronized across environments when you run home-manager switch.