Update dependencies and documentation

doc/internal/params.el

@@ -10,7 +10,7 @@
  ;; run-type must be "executable"
  (run-target-short     . "org2gfm")
  ;; run-target-long will always prefix "bin/"
- (nix-latest           . "2.23.3")
+ (nix-latest           . "2.24.1")
  (nix-stable           . "2.18.5")
  (nixos-latest         . "24.05")
  (platforms            . "\n\

doc/nix-installation.md

@@ -43,7 +43,7 @@ Hopefully, this alleviates any worry about installing a complex program on your
 
 > **<span class="underline">NOTE:</span>** You don't need this step if you're running NixOS, which comes with Nix baked in.
 
-Though the latest version of Nix is Nix 2.23.3, we'll be installing the version that the last release of NixOS (24.05) uses, specifically Nix 2.18.5. As discussed in the included [introduction to Nix](nix-introduction.md), this version is considered stable by the Nix community.
+Though the latest version of Nix is Nix 2.24.1, we'll be installing the version that the last release of NixOS (24.05) uses, specifically Nix 2.18.5. As discussed in the included [introduction to Nix](nix-introduction.md), this version is considered stable by the Nix community.
 
 The following command calls the official installation script for the recommended version of Nix. Note, this script will require `sudo` access.
 

doc/nix-introduction.md

@@ -196,7 +196,7 @@ However, if industrial users move to flakes to address these problems, we have t
 
 ### Nix quick releases compete with stability<a id="sec-4-2-3"></a>
 
-The latest major version of the Nix package manager is currently Nix 2.23.3, but NixOS 24.05, the latest stable release of NixOS, uses Nix 2.18.5. NixOS is the primary way the Nix package manager gets used in the field. Far fewer users install Nix as a package manager atop another operating system. From a community perspective it makes sense to consider Nix 2.18.5 the stable release of the package manager. This version gets the most scrutiny and critical bug fixes.
+The latest major version of the Nix package manager is currently Nix 2.24.1, but NixOS 24.05, the latest stable release of NixOS, uses Nix 2.18.5. NixOS is the primary way the Nix package manager gets used in the field. Far fewer users install Nix as a package manager atop another operating system. From a community perspective it makes sense to consider Nix 2.18.5 the stable release of the package manager. This version gets the most scrutiny and critical bug fixes.
 
 As mentioned above, there are strong reasons to use still-experimental features, particularly flakes. However, APIs and calculated hashes change too frequently in experimental features from version-to-version. By sticking with the version used in NixOS, we get less breaking changes. For example, the [flake.lock](../flake.lock) file included with this project has calculated hashes for dependencies. These hashes were computed with Nix 2.18.5, and could change with later versions.
 

doc/nix-usage-flakes.md

@@ -266,7 +266,7 @@ After a successful call of `nix build`, you'll see one or more symlinks for each
 readlink result*
 ```
 
-    /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+    /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 Following these symlinks, we can see the files the project provides:
 
@@ -288,7 +288,7 @@ It's common to configure these “result” symlinks as ignored in source contro
 nix path-info .#org2gfm
 ```
 
-    /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+    /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 ## Running commands in a shell<a id="sec-4-6"></a>
 
@@ -401,7 +401,7 @@ nix shell --ignore-environment \
     --command which org2gfm
 ```
 
-    /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm/bin/org2gfm
+    /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm/bin/org2gfm
 
 What we do with local flake references can work just as well with remote flake references.
 
@@ -429,7 +429,7 @@ nix profile list
     Flake attribute:    packages.x86_64-linux.org2gfm
     Original flake URL: git+file:///home/shajra/src/nix-project
     Locked flake URL:   git+file:///home/shajra/src/nix-project
-    Store paths:        /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+    Store paths:        /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 If we want to uninstall a program from our profile, we do so by the index from this list:
 

doc/nix-usage-flakes.org

@@ -438,7 +438,7 @@ readlink result*
 #+end_src
 
 #+RESULTS: nix-build-link
-: /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+: /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 Following these symlinks, we can see the files the project provides:
 
@@ -467,7 +467,7 @@ nix path-info .#<<get("package-attr-short")>>
 #+end_src
 
 #+results: nix-build-path
-: /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+: /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 ** Running commands in a shell
 
@@ -629,7 +629,7 @@ nix shell --ignore-environment \
 #+end_src
 
 #+RESULTS: nix-shell-remote
-: /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm/bin/org2gfm
+: /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm/bin/org2gfm
 
 What we do with local flake references can work just as well with remote flake
 references.
@@ -680,7 +680,7 @@ nix profile list --profile /tmp/nix-profile | ansifilter
 : Flake attribute:    packages.x86_64-linux.org2gfm
 : Original flake URL: git+file:///home/shajra/src/nix-project
 : Locked flake URL:   git+file:///home/shajra/src/nix-project
-: Store paths:        /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+: Store paths:        /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 If we want to uninstall a program from our profile, we do so by the index from
 this list:

doc/nix-usage-noflakes.md

@@ -161,7 +161,7 @@ We can build this package with `nix-build` from the project root:
 nix-build --attr packages.x86_64-linux.org2gfm .
 ```
 
-    /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+    /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 If we omit the path to a Nix file, `nix-build` will try to build `default.nix` in the current directory. If we omit the `--attr` switch and argument, `nix-build` will try to build packages it finds in the root of the attribute tree.
 
@@ -173,7 +173,7 @@ The output of `nix-build` shows us where in `/nix/store` our package has been bu
 readlink result*
 ```
 
-    /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+    /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 Following these symlinks, we can see the files the project provides:
 

doc/nix-usage-noflakes.org

@@ -305,7 +305,7 @@ nix-build --attr <<get("package-attr-long")>> .
 #+end_src
 
 #+RESULTS: nix-build
-: /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+: /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 If we omit the path to a Nix file, =nix-build= will try to build =default.nix=
 in the current directory. If we omit the =--attr= switch and argument,
@@ -328,7 +328,7 @@ readlink result*
 #+end_src
 
 #+RESULTS: nix-build-link
-: /nix/store/vgsqy4nmsravl5dbi5vr4q88q8pq0xxz-org2gfm
+: /nix/store/pf0g885myl26nmcln8ldhzv5c7nx78vf-org2gfm
 
 Following these symlinks, we can see the files the project provides: