-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for nix #15
Comments
I on purpose try to limit users from adding invalid configs, I currently pick the root of your config (supporting monorepos) based on which init file you pick (init.lua / init.vim / .vimrc). Picking an init file is currently required in order to prevent users from adding completely irrelevant repositories. Do you have any ideas on how your config could be validated and an init file can be selected? |
Would it be possible to just parse the flake.nix file to figure out all plugins? Is there a way to validate that it is a config and not an unrelated nix project? Thanks for making the issue btw :D It's hard to build software for use cases that you don't know exist! |
That's why I'm not sure if it's feasible to add support for nix.
Technically, you don't need an init file. You could also just have files in I guess some other options for nix would be to grep for a neovim configuration like I think it would be a good idea to collect different nix use cases here for a while (or to collect unsupported use cases somewhere) before attempting to implement support. |
I've just came here report a similar issue. I also think that it is not an easy task to support nix based configurations. I agree that the best would be to collect various use-cases and maybe start from the simplest ones that could be added with the least effort. My configuration lives here https://github.com/ghostbuster91/dot-files/tree/master/programs/neovim . It is a mix of different approaches. Some of the plugins are taken directly from the nixpkgs, some are defined as overlays (to override existing ones) and some as new derivations. I have the |
One option you could maybe go for is to optionally support a ready-made metadata dump stored in the repo. (i.e. something like |
@nogweii See https://github.com/creativenull/dotfyle-metadata.nvim - it's a WIP and not yet supported by Dotfyle, but I will build a parser for it when I'm back from vacation. |
A really cool project!
I tried signing up with my config, but it fails on step 2, because it can't find the init file.
My init.lua doesn't exist in the dotfiles, because it's generated by nix (which I use to manage plugins).
I'm not sure if it would be feasible to add support for nix, but I've opened this issue just in case 😄
The text was updated successfully, but these errors were encountered: