Merge "Fix various links to anchors in documentation." into main

2025-05-02 11:45:29 +00:00
parent c88ce60e25 f659a1e638
commit 4e84fd9a00
10 changed files with 11 additions and 11 deletions
@@ -14,7 +14,7 @@ The moving parts of channels are:
 - The official channels listed at <https://nixos.org/channels>
 - The user-specific list of [subscribed channels](#subscribed-channels)
 - The [downloaded channel contents](#channels)
- The [Nix expression search path](@docroot@/command-ref/conf-file.md#conf-nix-path), set with the [`-I` option](#opt-i) or the [`NIX_PATH` environment variable](#env-NIX_PATH)
+- The [Nix expression search path](@docroot@/command-ref/conf-file.md#conf-nix-path), set with the [`-I` option](#opt-I) or the [`NIX_PATH` environment variable](#env-NIX_PATH)

 > **Note**
 >
@@ -22,7 +22,7 @@ left untouched; this is not an error. It is also not an error if an
 element of *args* matches no installed derivations.

 For a description of how *args* is mapped to a set of store paths, see
-[`--install`](#operation---install). If *args* describes multiple
+[`--install`](install.md). If *args* describes multiple
 store paths with the same symbolic name, only the one with the highest
 version is installed.

@@ -256,13 +256,13 @@ To build with one of those environments, you can use
 $ nix build .#nix-ccacheStdenv
 ```

-for flake-enabled Nix, or
+for <a id="nix-with-flakes">flake-enabled Nix</a>, or

 ```console
 $ nix-build --attr nix-ccacheStdenv
 ```

-for classic Nix.
+for <a id="classic-nix">classic Nix</a>.

 You can use any of the other supported environments in place of `nix-ccacheStdenv`.

@@ -101,7 +101,7 @@

  See [File System Object](@docroot@/architecture/file-system-object.md) for details.

-  [file system object]: #gloss-file-system-object
+  [file system object]: #gloss-store-path

 - [store object]{#gloss-store-object}

@@ -164,7 +164,7 @@ Note that lists are only lazy in values, and they are strict in length.

 An attribute set is a collection of name-value-pairs (called *attributes*) enclosed in curly brackets (`{ }`).

-An attribute name can be an identifier or a [string](#string).
+An attribute name can be an identifier or a [string](#type-string).
 An identifier must start with a letter (`a-z`, `A-Z`) or underscore (`_`), and can otherwise contain letters (`a-z`, `A-Z`), numbers (`0-9`), underscores (`_`), apostrophes (`'`), or dashes (`-`).

 > *name* = *identifier* | *string* \
@@ -13,7 +13,7 @@

 - The `discard-references` feature has been stabilized.
  This means that the
-  [unsafeDiscardReferences](@docroot@/contributing/experimental-features.md#xp-feature-discard-references)
+  `unsafeDiscardReferences`
  attribute is no longer guarded by an experimental flag and can be used
  freely.

@@ -3,4 +3,4 @@ name: auto-allocate-uids
 internalName: AutoAllocateUids
 ---
 Allows Nix to automatically pick UIDs for builds, rather than creating
-`nixbld*` user accounts. See the [`auto-allocate-uids`](#conf-auto-allocate-uids) setting for details.
+`nixbld*` user accounts. See the [`auto-allocate-uids`](../command-ref/conf-file.md#conf-auto-allocate-uids) setting for details.
@@ -3,4 +3,4 @@ name: cgroups
 internalName: Cgroups
 ---
 Allows Nix to execute builds inside cgroups. See
-the [`use-cgroups`](#conf-use-cgroups) setting for details.
+the [`use-cgroups`](../command-ref/conf-file.md#conf-use-cgroups) setting for details.
@@ -209,7 +209,7 @@ For example, you could build from a specific version of Nixpkgs with something l
 $ nix build -f "https://github.com/NixOS/nixpkgs/archive/refs/heads/release-24.11.tar.gz" firefox
 ```

-If a *fileish* starts with `flake:`, the rest of the argument is interpreted as a [flakeref](./nix3-flake.md#flake-reference) (see `nix flake --help` or `man nix3-flake`), which requires the "flakes" experimental feature to be enabled.
+If a *fileish* starts with `flake:`, the rest of the argument is interpreted as a [flakeref](./nix3-flake.md#flake-references) (see `nix flake --help` or `man nix3-flake`), which requires the "flakes" experimental feature to be enabled.
 This is is *not quite* the same as specifying a [flake output attrpath](#flake-output-attribute).
 It does *not* access the flake directly and does not even consider the existence of flake.nix, but instead fetches it as if it is not a flake at all and `import`s the unpacked directory.
 In other words, it assumes that the flake has a `default.nix` file, and then interprets the attribute path relative to what `default.nix` evaluates to.
@@ -50,7 +50,7 @@ R""(
 # Description

 `nix shell` runs a command in an environment in which the `$PATH` variable
-provides the specified [*installables*](./nix.md#installable). If no command is specified, it starts the
+provides the specified [*installables*](./nix.md#installables). If no command is specified, it starts the
 default shell of your user account specified by `$SHELL`.

 )""