Neovim - adhityaravi/fire-flake GitHub Wiki

Neovim configured to be beautiful with feature-rich plugins and a focus on usability. This setup is designed to be beginner-friendly while still providing advanced features for experienced users.

Right off the bat, this setup doesnt use any dynamic package managers to install packages but rather nixpkgs and NUR. Maybe this is already clear from the philosophy behind flakes - This is to make sure the config is entirely declarative, reproducible and pure according to nix. So similar to other modern Neovim configs, you can update the upstream to update all the plugins but unsimilar to others, you have to do it via Nix Home-Manager.

That said, I plan to use the import functionality of lazy.nvim to lazy load the plugins. So lazy.nvim can be used to add your own flavors without having to wait for upstream changes. This, ofcourse, means you main these and not fire-flake. And it will tarnish your Neovim setup from being nix pure.

Some cool and well-maintained Neovim configs that inspire me -

• NvChad
• LazyVim
• AstroNvim
• LunarVim

I plan to add some specalized plugins for my work (TBD) with an opt-out option.

Also, I am relatively new to lua and neovim, (and actually the nix ecosystem) so I am still learning the ropes. I am learning by doing, so I cant claim (yet) that the plugis or how its implemented is performant. But that's the plan.

• Lazy load plugins where possible to reduce startup time. (WIP)
• Expose plugins and configurations in the home.nix file for user customization.
• Start big and trim down later. So while it might seem bloated, I plan to remove plugins that are not useful or are too heavy.
• Some plugins intentionally overlap in functionality (e.g., Spectre vs. Telescope's grep) to allow flexibility and tool specialization.
• Initially considered Codeium and Windsurf for AI features but they were less stable or cumbersome to configure — defaulted to Copilot for now.
• which-key.nvim is preferred over mini.clue due to its beginner-friendly interface, although many recommend mini.clue for performance and minimalism. Both are available but only which-key is exposed in the profile for now.

home.nix user profile allows customization of the default neovim setup:

# Neovim
custom.neovim = {
  enable = true;

  # Example: Add extra plugins
  extraPlugins = with pkgs.vimPlugins; [
   catppuccin-nvim
  ];

  # Example: Add extra Lua config
  extraLuaConfig = ''
   vim.cmd("colorscheme catppuccin")
   require("catppuccin").setup({})
  '';
};

The module can be imported and configured in the home.nix under the profile directory in the user profile path /profile/user/

While this is a flexibility I want to have, I only intend to use it for enabling or disabling plugins provided by the fire-flake flavored neovim setup. So that, the same module can be used with different setups for different profiles.

But, it still allows entire neovim configurations from home.nix. But no one sane will do it, rather use a package manager like lazy.nvim (comes with fire-flake) to do it if you need personilizations that upstream doesnt provide.

• plenary.nvim
• nvim-web-devicons
• mini.nvim

• which-key.nvim
• noice.nvim
• hydra.nvim
• auto-save.nvim

• lualine.nvim
• toggleterm.nvim
• alpha-nvim
• persistence.nvim
• bufferline.nvim
• smart-splits.nvim
• leap.nvim

• catppuccin
• rose-pine
• tokyonight.nvim
• kanagawa.nvim
• oxocarbon.nvim
• everforest
• gruvbox.nvim
• nightfox.nvim
• edge
• onedarkpro.nvim
• dracula.nvim
• monokai-pro.nvim
• cyberdream.nvim

• nvim-treesitter

Language support enabled for: bash, go, python, terraform, nix, lua, json, yaml, markdown.

• nvim-lspconfig
• mason.nvim
• mason-lspconfig.nvim
• lspkind.nvim

• nvim-cmp
• cmp-nvim-lsp
• cmp-buffer
• cmp-path
• cmp-cmdline
• copilot.lua

Provides AI-assisted suggestions and standard autocomplete.

• telescope.nvim
• telescope-project.nvim
• telescope-file-browser.nvim
• nvim-spectre
• grapple.nvim

• nvim-tree.lua

• nvim-dap
• nvim-dap-ui
• nvim-dap-python
• nvim-dap-go
• neotest
• neotest-go
• neotest-python
• neotest-plenary
• nvim-bqf

• gitsigns.nvim
• lazygit.nvim
• octo.nvim

vim.g.mapleader = " "
vim.g.maplocalleader = " "

The following plugins require you to log in to their respective services:

• Copilot — enabled by default. Use :Copilot auth to authenticate.
• Octo.nvim — GitHub functionality. Use gh auth login to authenticate.

Refer to each plugin's documentation for advanced configuration and troubleshooting.

• Lazy load plugins with lazy.nvim to reduce startup time.
• Organize plugin imports in init.lua.
• Improve auto-completion performance.

• Make selected plugins (TBD) optional for users to enable/disable in home.nix.
• Add oil for file management in the buffer.
• Add mapple for note taking.
• Add autopairs for auto-pairing characters.
• Add spider for better text navigation.
• Add todo-comments.

• Add colorizer for visualizing colors in code.
• Add conform for better formatting.
• Add indent-blankline for showing indentation guides.

• Group plugins by functionality for better organization.

Some suggest this is too many plugins; others say it's not enough. For now, this setup is tuned for personal comfort and will evolve over time as preferences change.

Many parts of this will raise the comment "but youre re-building the wheel" and yes, I might be doing that to learn wtf is going on or to maybe compensate some disadvantages of a static configuration model.