Document import <path> syntax #3159
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There is no <para>Paths can also be specified between angle brackets, e.g.
<literal><nixpkgs></literal>. This means that the directories
listed in the environment variable
<envar linkend="env-NIX_PATH">NIX_PATH</envar> will be searched
for the given file or directory name.
</para> |
This reverts commit d8730fb.
|
@edolstra, that makes perfect sense. I didn't realize that paths can be written with angle brackets, which of course is implied by the fact that I do think that for beginners coming from other languages where What do you think? |
zimbatm
approved these changes
Oct 22, 2019
|
Thanks! |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #338 by changing the start of the manual section on
builtins.importto the following:import path, import <path>, builtins.import path, builtins.import <path>
Load, parse and return the Nix expression in the file path. If path is a directory, the file default.nix in that directory is loaded. If the <path> syntax is used, the path will be resolved relative to those listed in the NIX_PATH environment variable (see the section on NIX_PATH for details on how the resolution works). Evaluation aborts if the file doesn’t exist or contains an incorrect Nix expression. import implements Nix’s module system: you can put any Nix expression (such as a set or a function) in a separate file, and use it from Nix expressions in other files.