Fernando Ayats

If you want to write the implementation in a separate PR I'd be happy to review. But I have other projects on the top of my stack for me to...

You can evaluate this expression without `callPackage` or `builtins.functionArgs` with `import ./test.nix (with import {}; {inherit hello symlinkJoin lib;})`

I do agree that this might be or not an issue depending on how we define "using"...

I also get this issue on neovim 0.10.

It might be some race condition or weird interaction with the configuration of tree-sitter's foldexpr: https://github.com/nvim-treesitter/nvim-treesitter?tab=readme-ov-file#folding Disabling these two lines from my configuration fixes the issue. I will try this:...

I'll fix it asap

Please run the command with `--verbose` and paste the output.

This happens because WM tries to modify symlinks in-place. To make things simpler, I should probably create a new derivation, create the new destkop files there, and then merge the...

Now that I look into it, using `buildEnv` instead of `symlinkJoin` could solve these issues, as it unrolls all the symlinks...

At the point that I'm fighting against symlinkJoin/lndir/buildEnv, I might as well write my own symlinker (#27)