How do you install mason? Or do you use something instead?

Read the comments of spec. For more references, seehttps://github.com/azuwis/nix-config/tree/master/common/lazyvim

So you don't use mason at all. Do you use anything else to maintain and install lsps?

Use

    programs.neovim.extraPackages = with pkgs; [      lua-language-server      ansible-language-server      terraform-ls    ];

Thank you for your kind replies. Greatly appreciated.

I added a lua dir (empty) and I'm no longer getting an error but I still don't have an init.lua

[09:02:54] dylan@maple-nix /home/dylan/.config/nvim  > tree . -l.├── lua -> /nix/store/qm0gc3ac6f1rz3dnwawl4i4v1na3rxmp-home-manager-files/.config/nvim/lua└── parser -> /nix/store/qm0gc3ac6f1rz3dnwawl4i4v1na3rxmp-home-manager-files/.config/nvim/parser    ├── c.so -> /nix/store/1g417k76s5j7cw6lkqwlrsz2j9adba63-c-grammar-0.0.0+rev=212a80f/parser    └── lua.so -> /nix/store/s0ksvj9s75ih71x6qwlbphzmgqlir0lr-lua-grammar-0.0.0+rev=9668709/parser3 directories, 2 files

Missingprograms.neovim.enable = true

Thanks for the quick reply.

I decided to usenixvim instead.

A demo to setup LazyVim using NixVimhttps://github.com/azuwis/lazyvim-nixvim/tree/master

nix run github:azuwis/lazyvim-nixvim

@azuwis Any idea how to also include treesitter parsers in the nixvim flake?

https://nix-community.github.io/nixvim/plugins/treesitter/index.html should work.

It did not, since rtp gets cleared when lazy.nvim starts :)
I got it working now though with some fixes

A demo to setup LazyVim using NixVimhttps://github.com/azuwis/lazyvim-nixvim/tree/master

nix run github:azuwis/lazyvim-nixvim

I really like this. But what i don't get. How can i use the LazyExtras. First of all how does it working through the IDE, cause i can't find the settings it does? -> ok this is comming by default with LazyVim found under lazyPath from nix config. So i think the json just activates it then. So then i just need to find out how to overwrite the lua configs with nix and how to manage lazyvim.json with nix

And second, how can i insert the lazyvim.json in nix (the file which saves the enabled extras)?

Same issue here, not (yet) gone for me. Replying to keep the discussion active

Remove those lines if you don't setup any LazyVim plugins:

            -- import/override with your plugins            { import = "plugins" },

Yup, that removed the error! Could you explain to me what that does? I don't have much understanding of the Nix language, so I simply copy-pasted your code 😅

This seems to have fixed itself, not sure how but I'm not going to complain.

I think I see what happened. Removing{ import = "plugins" } indeed makes the error go away, but it also goes away when specify a LazyVim plugin you want to use (inlua/plugins/some-plugin.lua).

i am trying to override some of the configuration that lazyvim has setup, and I am so very confused on to do this, given the fact that lazyvim is being setup by nixvim through theextraConfigLua property.
So when you 'lua/plugins/some-plugin.lua' is this lua directory in .config ? So does that mean, to write this config 'nix way' i make a .lua file in my nix directory and then tell nix to copy this .lua into .config directory?

Here is my configuration, (i am trying to implement the@azuwis way of things but in my home-manager)https://github.com/shivajreddy/dotfiles/blob/main/home/apps/nixvim/default.nix

Using vimPlugins from nixpkgs make the setup reproducible, and works in air-gapped environment.

In Nix, the build binary cache can be shared usingnix-store --serve,Cachix or similar, make the setup much faster it you manage hundreds of machines.

You can make the plugin an empty list[], then lazy.nvim will download all plugins.

Maybe share a little configuration? It's not clear from context whatobsidian.lua is referring to. Do you haveobsidian-nvim in my list of Nix packages? eg.

...extraLuaConfig=letplugins=withpkgs.vimPlugins;[# LazyVimLazyVim...obsidian-nvim...

how could I copy all the downloaded stuffs to another offline machine so that I could bundle the dev env in ci and copy them on those offine machines

@qlibp you look at my dotfiles and the nvim config, i added comments there on how to get lazyvim to get to work with nixos.

can I use it on non-nixos machine？

Same for me, related#3702

require("lazy").setup({...spec= {          {"LazyVim/LazyVim",import="lazyvim.plugins"},...          {"nvim-treesitter/nvim-treesitter",opts=function(_,opts)opts.ensure_installed= {}end,          },        },      })

This seems to do the trick.

Try add this to your lazyvim spec:

  {    "catppuccin/nvim",    name = "catppuccin",    enabled = false,  },  {    "folke/tokyonight.nvim",    enabled = false,  },  {    "LazyVim/LazyVim",    opts = {      colorscheme = "<theme_name>",    },  }

Thanks.
Apparently the name used to import by lazy was different from the name on vimPlugins, and that preventing neovim fom actually finding the plugin.

I had it asno-clown-fiesta-nvim on my nix file, but had to useno-clown-fiesta on my lua file.
Apparently it was defaulting to TokyoNight after not finding the plugin.

I don't know what the cattpuccin was all about..

Ok, tried a few different approaches, and got it workng by simply adding the following code to alsp.nvim file.

return {  {    "neovim/nvim-lspconfig",    opts = {      servers = {        nil_ls = {},        nixd = {},      },    },  },}

Nice work on this@matadaniel!

Something along these lines seems like the most sustainable approach. Some would likely argue it should be refactored to integrate with nixvim and eventually be able to take advantage of the work there on providing modules for other plugins not included in LazyVim+extras.

Thank you!

I have not had a good look at everything that nixvim has to offer as most of what I need is provided by LazyVim. The few plugins I configure myself were brought in from my old setup without nix. The module lets me use the same configuration and has lazy.nvim take care of everything, just as it always has.

Yea possibly there's no need. I'm not sure if you get a bit of type safety for free by reusing the nixvim modules a bit more likenvix since you're already manually including binding for each of the lazyvim extras (e.g.here and the other leaves of thelazyvim/extra tree). I don't know enough about how lazyvim itself functions to be sure if there's a significant difference to replicating each of its plugins/extras in nix modules or pushing everything down to the direct management of LazyVim/lazy.nvim. It's possible what you've done here is the best way to avoid a situation where you'd have to essentially copy and paste lots of lua from the LazyVim repo itself into a system designed to mirror it from nix. The latter is obviously not desirable!

In any case, this is probably worthy of separate discussion in LazyVim-module's issues. Many thanks again for putting this together!

@azuwis your solution is certainly a great way to get started here so many thanks for posting this nice solution and creating the discussion. I'd be curious to know if you agree@matadaniel's home-manager module provides a sane way to maintain a feature-complete and extensible mirror of lazyvim that's accessible from nix. It would be nice to eventually coalesce around a single repo that could become a candidate to include in nix-community or similar.

I created a place to discuss LazyVim on Nix:matadaniel/LazyVim-module#5. Please share your thoughts!

Two things I forgot to mention:

1. I haveNVIM_APPNAME=lazyvim in my environment. I you don't, link the files to.config/nvim instead of.config/lazyvim to make it work.
2. If you would want to lock your plugin versions, you can also link the lock-file.

xdg.configFile."lazyvim/lazyvim.json"={source="${inputs.lazyvim}/lazyvim.json";};

But then you cannot update via lazy.nvim, since it will obviously be read only.
I don't care though and if i really need to because smth broke, I just manually copy the lock-file from my main system to another machine.

Hi@Nikola-Milovic, it looks like there's both aharpoon2 andluasnip extra for lazyvim

i tried it on my setup and it looks like the secret sauce is that lazyvim extras expects it to be harpoon instead of harpoon2.. it looks like the same requirement for luasnip (LuaSnip instead of luasnip)

after rebuilding your home manager config, go to lazy extras and enable:

result:

Thank you! Very interesting! So basically for some packages I have to update the name to match to whateverrequire("name") specifies?

looks like it, if you want to use those plugins as lazy extras 😆

i think it relates to the lightblue names in Lazy extras.. maybe someone more knowledgeable can chime in

            path = "${lazyPath}",            patterns = { "." },            -- fallback to download            fallback = true,

This is incorrect.

You're right. I believe the code ishttps://github.com/folke/lazy.nvim/blob/56ead98e05bb37a4ec28930a54d836d033cf00f2/lua/lazy/core/meta.lua#L219

It works by coincidence:

$ nvim --headless -c ':lua for _, plugin in ipairs(require("lazy").plugins()) do print(plugin.url) end' -c 'q'https://github.com/hrsh7th/cmp-path.githttps://github.com/nvim-lua/plenary.nvim.githttps://github.com/folke/noice.nvim.githttps://github.com/akinsho/bufferline.nvim.git...

All the plugins url contains a..

yes that is the code for it :)

Ah yeah that is quite funny XD

It wasnt working by accident for nixCats in the lazy.nvim wrapper, not sure why that is, although I am using the shorthand urls, but doesnt really matter "" works better and is more correct anyway

Well, plugins is a thing created directly in the code snippet you followed. extraPackages isnt, extraPackages is actually part of the module, and you can look up what it does

This takes that plugins list and makes them into a lazyPath variable which you presumeably then told lazy about.

mkEntryFromDrv=drv:iflib.isDerivationdrvthen{name="${lib.getNamedrv}";path=drv;}elsedrv;lazyPath=pkgs.linkFarm"lazy-plugins"(builtins.mapmkEntryFromDrvplugins);

Thanks! But I was talking about

plugins = with pkgs.vimPlugins; [      lazy-nvim    ];

not the one inside the let-binding, but the one for theprograms.neovim config. Or are you indeed talking about theprograms.neovim.plugins?

Using lua to configure neovim and using nix to install plugins, language servers, tools and so on, is pretty much the best possible combination, and very aligned with what nix does well.

No, I get that. But is it well aligned with what Neo/LazyVim do best? I mean, a huge part of the reason to use Neo/Lazy is the ability to iterate over configuration and plugin combinations almost instantly. And the rollback/version control use cases are completely covered by LazyVim + Git (or other VCS).

I feel like by managing N/L with Nix you introduce unnecessary complexity in the middle of that quick iteration/instant feedback process without adding significant benefits. This is especially felt when you're in the middle of working and want to quickly remove some annoyance or improve experience without losing the flow.

Then again, perhaps I'm crazy.

I have the lua outside of the nix, I'm not a fan of writing one language in another, it makes it harder to debug in general. I'm using home-manager for basic setup and configuration. Apps like neovim etc I configure as separate flakes and profiles I install. Iterating over neovim configuration in a flake doesn't force a home-manager rebuild and running anix build or even better, anix run .#nvim in my case allows me to test really quickly. The benefit outweighs the few extra seconds I have to wait. Also, at the end of it I have a portable neovim configuration I can run on any nix enabled machine, without installation. I'm sure you are aware of these party tricks already. I think one of the issues here is that a lot of folks put everything into one home-manager setup, and iterating over small changes do take some time, rendering them cumbersome in some cases.

I'm sure you are aware of these party tricks already.

You give me too much credit. I am not, just getting familiar with Nix. I have to fiddle more with this. Thanks!

I started using this approach last month, which is when I started using NixOS for my desktop. It works fine IMO. I've used LazyVim for the past few years, Vim for little more than a decade. I agree that LazyVim does not work smoothly with Nix, but I think this is the best option for now due to the functionality of LazyVim (it just works) + reproducibility of Nix. Though I believe there's a plenty big room for improvement. I guess you can check outNixvim as an alternative. I'm planning to check it out in a near future when I have some time---the nix rabbit hole has already wasted my time enough for now 🥲

One way to retain the fast iteration of the nvim config (without the need tohome-manager switch after every change) is using a symlink:

home.file={".config/nvim".source=config.lib.file.mkOutOfStoreSymlink"${home.homeDirectory}/.config/home-manager/where/every/you/want/to/put/it/nvim";

Note, that there was abug in an old version of nix that prevented this from working.

Why is lazy removing/adding paths? It prevents me from having other directory and module paths under the lua directory.,

@folke would be great if you can shed some light. I am sure I've got something wrong somewhere...

before loading lazy.nvim
Lua package.path:
/nix/store/hxcwr8j33p9m437a7jyzwbzxhsyj5dh4-luajit-2.1.1713773202-env/share/lua/5.1/?.lua
/nix/store/hxcwr8j33p9m437a7jyzwbzxhsyj5dh4-luajit-2.1.1713773202-env/share/lua/5.1/?/init.lua

Lua package.cpath:
/nix/store/hxcwr8j33p9m437a7jyzwbzxhsyj5dh4-luajit-2.1.1713773202-env/lib/lua/5.1/?.so

Neovim runtime paths:
/nix/store/yim8xc6ngdj5k55dpqcz50icrsqk0hvy-nvim-config
/nix/store/l91x39p8wr8f4zqrs3cn7frjigzf142r-lazy-plugins
/nix/store/y2jn4p3ppm4gcgxzlad5x95b6fx9kz2n-vimplugin-lazy.nvim-2024-12-07
/nix/store/x137yfpy63v4mkn68fkaj5ky8yv53xwf-neovim-unwrapped-0.10.2/share/nvim/runtime
/nix/store/x137yfpy63v4mkn68fkaj5ky8yv53xwf-neovim-unwrapped-0.10.2/lib/nvim

after loading lazy.nvim
Lua package.path:
/nix/store/hxcwr8j33p9m437a7jyzwbzxhsyj5dh4-luajit-2.1.1713773202-env/share/lua/5.1/?.lua
/nix/store/hxcwr8j33p9m437a7jyzwbzxhsyj5dh4-luajit-2.1.1713773202-env/share/lua/5.1/?/init.lua

Lua package.cpath:
/nix/store/hxcwr8j33p9m437a7jyzwbzxhsyj5dh4-luajit-2.1.1713773202-env/lib/lua/5.1/?.so

Neovim runtime paths:
/nix/store/y2jn4p3ppm4gcgxzlad5x95b6fx9kz2n-vimplugin-lazy.nvim-2024-12-07
/nix/store/x137yfpy63v4mkn68fkaj5ky8yv53xwf-neovim-unwrapped-0.10.2/share/nvim/runtime
/nix/store/x137yfpy63v4mkn68fkaj5ky8yv53xwf-neovim-unwrapped-0.10.2/lib/nvim
/Users/christian/.local/state/nvim/lazy/readme

I loaded LazyVim in a separate module file... and restored the config path doing the following:

local function add_to_runtimepath(config_path)  if config_path and config_path ~= "" then    vim.o.runtimepath = vim.o.runtimepath .. "," .. config_path  endendlocal status, config_path = pcall(vim.api.nvim_get_var, "config_path")if status then  add_to_runtimepath(config_path)endreturn {  {    "LazyVim/LazyVim",    opts = {      colorscheme = "Catppuccin",    },    import = "lazyvim.plugins"  },}

LazyVim check ifmake,cmake,gmake is available when startup fortelescope-fzf-native.nvim, and try to build it.

In Nix, we probably don't want this behavior, and should enable or disable it explicitly.

If you dont needtelescope-fzf-native.nvim, you can setenabled = false and removetelescope-fzf-native.nvim from plugins.

LazyVim v14 makes fzf the default picker, so this is no longer necessary unless you explicitly enable the telescope extra.

@minusfive If you get a setup with LazyVim that you're happy with, please do share it, I ended up going a different route and I would like to do something similar to what you described

Also if you wanted to PR a LazyVim template I'd accept it, as long as it doesn't have many customizations or use things in LazyVim that are likely to change. (The kickstart template has been fairly low maintenance and I'd love to keep that trend haha)

@minusfive Although nixCats is an awesome package manager, my module has a more narrow focus on providing the experience you described with LazyVim and Home Manager.
https://github.com/matadaniel/LazyVim-module