https://staging.sua.dev/blog/neovim/Recent content in Neovim on ʕ•ᴥ•ʔHugoen-USCopyright © 2026, Justin Hoang.Thu, 23 Apr 2026 22:16:44 -0600https://staging.sua.dev/neovim/Fri, 05 Sep 2025 00:00:00 -0600https://staging.sua.dev/neovim/<ul> <li><a href="#repositories">Repositories</a></li> <li><a href="#plugins">Plugins</a></li> <li><a href="#quirks">Quirks</a></li> </ul> <h2 id="repositories">Repositories</h2> <p>My <code>Neovim</code> configuration is currently in two places: <a href="https://gitea.sua.dev/sua/nvim">nvim</a> and <a href="https://gitea.sua.dev/sua/nixvim">nixvim</a>. Both of these configurations were heavily inspired by <a href="https://github.com/nvim-lua/kickstart.nvim">kickstart.nvim</a>, a minimal starting point for Neovim with sensible out-of-the-box configurations and detailed documentation. The idea is that kickstart will give you the tools to build your own configuration, rather than providing everything like a distribution would (see <a href="https://www.lazyvim.org/">LazyVim</a> for example).</p> <p>I have mainly been using the nixvim configuration since last year. It is powered by the <a href="https://github.com/nix-community/nixvim">nixvim</a> project, a Neovim distribution powered by <code>nix</code>. It allows you to define your Neovim configurations using <code>nix</code> modules rather than typical <code>lua</code> files. This has the added advantage of build reproducibility and seamless integration into the rest of my <code>nix</code> system configuration.</p>