Plugins TODO

• swaits/zellij-nav.nvim // tmux
• kevinhwang91/nvim-ufo
• harpoon
• git-workspaces
• AI option (on/off) ?
• Note taking NeOrg (worth?)

Features TODO/TEST

• Python ecosystem (debugger, linter, ...)
• Golang ecosystem
• Lua ecosystem
• Nix ecosystem
• JS ecosystem (iuuhg)
• HTML/HTMX
• CSS/TailwindCSS
• Templ (?)

This is the help for the nixCats lazy wrapper

Or well, most of the help for it. There is also help for it at :h nixCats.luaUtils

It is the entirety of kickstart.nvim with very few changes, but uses nixCats to download everything

enter a new directory then run:

nix flake init -t github:BirdeeHub/nixCats-nvim#kickstart-nvim

then to build, nix build .

and the result will be found at ./result/bin/nvim

It also can work without any nix whatsoever. It has been adapted such that it works either way!

All notes about the lazy wrapper are in comments that begin with the string: NOTE: nixCats: so to find all of the info, search for that.

One other note.

If you install your grammars via lazy.nvim rather than nix, you will need to add a c compiler to your lspsAndRuntimeDeps section in your categoryDefinitions

If you install your grammars via nix, the only methods supported via the lazy.nvim wrapper are the following.

Summary: as long as pkgs.neovimUtils.grammarToPlugin is called on it somehow, it will work.

Any other ways will still work in nixCats, but not when using the lazy wrapper, because the lazy wrapper has to add them back to the runtimepath.

pkgs.vimPlugins.nvim-treesitter.withAllGrammars
# or
pkgs.vimPlugins.nvim-treesitter.withPlugins (plugins: with plugins; [
  nix
  lua
  # etc...
]);
# or
pkgs.vimPlugins.nvim-treesitter.withPlugins (plugins: pkgs.vimPlugins.nvim-treesitter.allGrammars)
# or
builtins.attrValues pkgs.vimPlugins.nvim-treesitter.grammarPlugins
# or
pkgs.neovimUtils.grammarToPlugin pkgs.tree-sitter-grammars.somegrammar

Disclaimer:

lazy.nvim technically works fine on with nix, HOWEVER it will block any other plugin manager, including nix, from installing anything on its own without also making a lazy.nvim plugin spec and making sure the names match.

This is the reason for the lazy.nvim wrapper provided by the luaUtils optional template.

It simply tells lazy about the location of things from nix, and sets a few compatibility options before calling the normal lazy setup function.

If you wish to download something from nix, the name lazy.nvim knows about and the name nix gave it must match. Otherwise, lazy.nvim will download it anyway.

For how to address that, see the main init.lua of this template. and search for NOTE: nixCats: