Hello there! A quick and maybe dumb question...

I am currently working on my home-manager configuration and decided to make my scripts into .nix files that evaluate strings (for interpolating packages). Now, if I do

{
  # ...
  text = import ./my-script.nix;
}

It yields an error, which is very non-descriptive... But:

{
  # ...
  text = import ./my-script.nix { pkgs = pkgs; };
}

Does not errors and the function is evaluated? I thought that parameters got passed down kind of like imports does, but it isn't the case... Can someone explain me better how functions are evaluated in the case of an import?

Hello there! A quick and maybe dumb question...

I am currently working on my home-manager configuration and decided to make my scripts into .nix files that evaluate strings (for interpolating packages). Now, if I do

{
  # ...
  text = import ./my-script.nix;
}

It yields an error, which is very non-descriptive... But:

{
  # ...
  text = import ./my-script.nix { pkgs = pkgs; };
}

Does not errors and the function is evaluated? I thought that parameters got passed down kind of like imports does, but it isn't the case... Can someone explain me better how functions are evaluated in the case of an import?

Thanks in advance!

In reply to @wizardlink:matrix.org

Hello there! A quick and maybe dumb question...

I am currently working on my home-manager configuration and decided to make my scripts into .nix files that evaluate strings (for interpolating packages). Now, if I do

{
  # ...
  text = import ./my-script.nix;
}

It yields an error, which is very non-descriptive... But:

{
  # ...
  text = import ./my-script.nix { pkgs = pkgs; };
}

Does not errors and the function is evaluated? I thought that parameters got passed down kind of like imports does, but it isn't the case... Can someone explain me better how functions are evaluated in the case of an import?

Thanks in advance!

imports is actually a nixpkgs/nixos specific thing, it calls the "modules" (really functions) with a bunch of pre-defined arguments (see e.g. nixpkgs/lib/modules.nix if curious).

import on the other hand is a Nix keyword that parses and loads the expression from some path, and the attrSet it takes here (in your case { pkgs = pkgs; } is an argument passed to the function found in ./my-script.nix.

the start of your ./my-script.nix file likely looks something like this:

{ pkgs }:

Here, { pkgs }: is actually an anonymous function taking an attrSet with an attribute called pkgs.