NixOS/nix
NixOS/nix
1
0
Fork 0
mirror of https://github.com/NixOS/nix synced 2024-10-18 14:32:45 -04:00
Code Activity
nix/doc/manual/source/language/constructs/lookup-path.md

25 lines
716 B
Markdown
Raw Normal View History

introduce lookup paths as a distinct language construct so far they did not really have a name, and were at best referred to as "angle bracket syntax".
2023-10-06 21:10:20 -04:00
# Lookup path
> **Syntax**
>
annotate admonitions showing syntax also fix typos
2023-10-09 18:32:36 -04:00
> *lookup-path* = `<` *identifier* [ `/` *identifier* ]... `>`
introduce lookup paths as a distinct language construct so far they did not really have a name, and were at best referred to as "angle bracket syntax".
2023-10-06 21:10:20 -04:00
add cross-references to `nix-path` overriding (#11288) * add cross-references to `nix-path` overriding while this information is already present in the settings, it's more likely to be first accessed through the "lookup path" page, which currently requires following two links to get to the practically important bits. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2024-08-13 13:22:32 -04:00
A lookup path is an identifier with an optional path suffix that resolves to a [path value](@docroot@/language/types.md#type-path) if the identifier matches a search path entry in [`builtins.nixPath`](@docroot@/language/builtins.md#builtins-nixPath).
The algorithm for lookup path resolution is described in the documentation on [`builtins.findFile`](@docroot@/language/builtins.md#builtins-findFile).
introduce lookup paths as a distinct language construct so far they did not really have a name, and were at best referred to as "angle bracket syntax".
2023-10-06 21:10:20 -04:00
> **Example**
>
> ```nix
> <nixpkgs>
>```
>
> /nix/var/nix/profiles/per-user/root/channels/nixpkgs
> **Example**
>
> ```nix
> <nixpkgs/nixos>
>```
>
> /nix/var/nix/profiles/per-user/root/channels/nixpkgs/nixos
Copy permalink