This is awesome but....

[niksingh710]

but i think the architecture of nvim some how limits how it is working on nix.
nixvim some how managed to get neovim purely under them.

Somethings from there can be adapted like how they are handling the binary and how to modularize most of the stuff.

[Bot-wxt1221]

The goal of this project is using nvchad without any modficition for me. It is not for replacing nixvim.

[cbaconnier]

Using the nvchad-starter feature from nix4nvchad, I can use my own repository for the config and it gives me the freedom for my config and binaries from nixos. Plus, nvim config can also be used outside of nixos.

This is what I have done:

  nvchad-starter = {
      url = "github:cbaconnier/nvim";
      #url = "path:/home/clement/Projects/cbaconnier/nvim";   
      flake = false;
    };
  nvchad4nix = {
    url = "github:nix-community/nix4nvchad";
    inputs.nixpkgs.follows = "nixpkgs";
    inputs.nvchad-starter.follows = "nvchad-starter";
  };

binaries: https://github.com/cbaconnier/nixos-config/blob/6fc00a08087806b3e219998ad3d1a56a03712bb7/home-manager/nvim/default.nix
nvchad (really simple config at the moment): https://github.com/cbaconnier/nvim

So far, my pain point is testing / changing my nvim configuration. My current workflow is;

• Update the nvchad-starter url to my local path
• Do the changes in nvchad - nvim
• Rebuild nixos
• Repeat
• Once I'm done, commit nvchad - nvim
• Updating nvchad-starter url with the repository
• Commit
• 😮‍💨

I will probably use a VM to configure nvim because in the end I feel like it will be easier this way.
But this workflow is most probably a lack of knowledge from me.